Public | Automated Build

Last pushed: 8 months ago
Short Description
Full Description

HTTPS Everywhere

Getting Started

Get the packages you need and install a git hook to run tests before push:


Run all the tests:


Run the latest code and rulesets in a standalone Firefox profile:

bash test/ --justrun

Run the latest code and rulesets in a standalone Chromium profile:

bash test/ --justrun

Build the Firefox extension as a .xpi package:


Build the Chromium extension as a .crx package:


Both of the build commands store their output under pkg/.

Precommit Testing

One can run the available test suites automatically by enabling the precommit
hook provided with:

ln -s ../../hooks/precommit .git/hooks/pre-commit

Source Tree

This is the source tree for HTTPS Everywhere for Firefox and Chrome.

Important directories you might want to know about

src/                      The Firefox source

chromium/                 The Chromium/Chrome source
                          (not to be confused with Firefox browser "chrome" or UI)

src/components            |
src/chrome/content        | Firefox JavaScript and XUL code
src/chrome/content/code   |

src/chrome/content/rules  The rulesets live here

test/                     The tests live here

Hacking on the Source Code

The current stable release series is 5.2. The maintainers release new versions
off the current master branch about every two weeks.

To submit changes, either use pull requests on GitHub or email patches to (rulesets) or (code).

Writing rulesets

HTTPS Everywhere consists of a large number of rules for switching sites from HTTP to HTTPS. You can read more about how to write these rules here:

If you want to create new rules to submit to us, we expect them to be in the src/chrome/content/rules directory. That directory also contains a useful script, make-trivial-rule, to create a simple rule for a specified domain. There is also a script called, to check all the pending rules for several common errors and oversights. For example, if you wanted to make a rule for the domain, you could run

bash ./make-trivial-rule

inside the rules directory. This would create, which you could then take a look at and edit based on your knowledge of any specific URLs at that do or don't work in HTTPS. You should then run


to make sure that your rule is free of common mistakes.

Writing translations

If you would like to help translate HTTPS Everywhere into your language,
you can do that through the Tor Project's Transifex page:

Bug trackers and mailing lists

We currently have two bug trackers. The one on GitHub ( is recommended because it gets checked more frequently and has a friendlier user interface. The one on ( has a large backlog of bugs at this point, but it has the advantage of allowing you to post bugs anonymously using the "cypherpunks" / "writecode" account. (Note that you won't see replies unless you put an email address in the CC field.)

We have two publicly-archived mailing lists: the https-everywhere list ( is for discussing the project as a whole, and the https-everywhere-rulesets list ( is for discussing the rulesets and their contents, including patches and git pull requests.


There are some very basic unittests under test/. These are run with


Please help write more unittests and integration tests!

There are also ruleset tests, which aim to find broken rulesets by actually
loading URLs in a browser and watching for Mixed Content Blocking to fire.
The easiest way to run ruleset tests is to load a standalone Firefox instance
with the tests enabled:

bash test/ --justrun

Then click the HTTPS Everywhere icon on the toolbar, and click "Run HTTPS
Everywhere Ruleset Tests." When you run the tests, be prepared to let your
computer run them for a really long time.

Docker Pull Command
Source Repository