mozilla-firefox/firefox

Adopt this if you intend to build or patch Firefox itself; if you only want to use a browser, install a release or Nightly build instead.

The problem

Someone who wants to fix a Firefox behaviour, study how a browser feature is implemented, or ship a downstream build needs the actual product source, not a mirror or a bug tracker. Before, that canonical code lived on Mozilla's Mercurial servers, which meant Git-centric developers had to learn a different version-control workflow before they could even read history. The move to GitHub puts the code on the platform most developers already use, so cloning and browsing history follows familiar steps. The result is easier entry to the codebase, but the surrounding workflow — bugs, review, CI — does not move with it.

What's different

This repository is the browser product itself, including the Gecko engine and the front-end written largely in JavaScript, rather than a wrapper, extension or a community fork. A Mozilla staff member, writing about the migration, explained that only the code moved: Bugzilla remains the issue tracker, Phabricator handles code review and landing, and Taskcluster runs CI (comment summary). Mercurial servers still exist and are synced from GitHub, so automated systems can migrate gradually, and the "try" repository used to run CI on work-in-progress patches still runs on Mercurial. That split is the key trade-off: you get GitHub familiarity for reading and cloning, but filing a bug or landing a change still sends you to Mozilla's own tooling.

Who should try it

Good fit: someone who wants to read Gecko code, reproduce a bug locally, or build a patched browser, especially anyone already comfortable with Git. A related discussion noted a CLAUDE.md file pointing to AGENTS.md in the repository, which may matter if you want a coding assistant to navigate the tree (thread). Poor fit: people looking for a stable browser to install — release channels and Nightly builds are the right path. Also a poor fit for anyone expecting GitHub Issues and pull requests to be the contribution workflow.

Requirements and limitations

Building Firefox is a substantial setup: the project's own contribution quick reference and Firefox Source Docs are the real starting points, since the README here is deliberately short. Expect platform-specific build prerequisites and a long initial build. Issue tracking lives on Bugzilla, so searching for known problems means leaving GitHub. Questions go to the Matrix introduction channel rather than to the repository. The license is listed as NOASSERTION, so check the project's licensing terms before redistributing a build.

HotRepo's take

HotRepo has only one dated observation: on 2026-10-28 the repository sat at 13,628 stars with +23 that day and ranked on the daily board. One snapshot cannot establish a trend, so persistence of interest here is not yet judgeable. The larger public signal is the migration discussion itself, with 466 comments on the 2025-05-13 thread (discussion). Before investing, confirm on the contribution docs which workflow your target change actually requires.