Update cadence
- Mozilla patch release: target update within 7 days.
- Mozilla major release with MFSAs: target update within 48 hours.
- In-the-wild CVE against the pinned Firefox version: same-day.
- Disclosed zero-day: immediate security bump and rebuild.
Two layers of freshness enforcement
The launcher refuses a build classified STALE or CRITICAL unless a one-off override is used. An in-process gate rechecks at browser-window load and every 60 minutes, quitting when the build is a major version behind or affected by an in-the-wild issue, and warning when it is a patch version behind.
Qualification: the network check is fail-open when the network itself fails. gjoa status reports when the probe last succeeded so “verified safe” can be distinguished from “could not verify.”
Regression gates
Public stewardship documents describe gates for security-tagged patch persistence, non-patch mitigation assertions, scriptlet-bundle integrity, and patch-hash drift. A security-tagged patch that no longer applies is intended to stop the build.
Qualification: the security-tagged patch gate is currently vacuously green because the public source says zero patches carry that tag today. The gate arms when one is added.
Current public egress audit
This build makes 1 unattended network call: the Firefox version check.
That audit identifies itself as Gjoa 0.4.1, generated 2026-07-27 for audited commit 5f65774. The current source displayVersion is 0.4.2, so this site does not project the older audit forward as proof of the newer source state.