A security-focused, Chromium-based browser for desktop Linux inspired by Vanadium. This fork targets Debian x86_64.
- Desktop-relevant patches from Vanadium (located in vanadium_patches)
- Changes that increase hardening against known and unknown vulnerabilities
- Changes that make secondary browser features opt-in instead of opt-out (for example, making the password manager and search suggestions opt-in)
- Changes that disable opt-in metrics and data collection, so long as they have no security implications
- Any changes that sacrifice security for "privacy" (for example, enabling MV2) why?
- Any novel functionality that is unrelated to security
Upstream support is provided via secureblue. This fork is Debian‑only and is intended for local builds on modern Debian x86_64. Fedora/secureblue packaging is not supported here.
For Debian (x86_64) local builds based on ungoogled-chromium, see
docs/BUILDING_DEBIAN.md.
Some additional preferences are added to chrome://settings/security, these provide additional security and privacy controls should they be needed. An example of one toggle is the Network Service Sandbox (disabled by default), which is known to occasionally clear cookies on exit.
There is also a Website Dark Mode preference added to chrome://settings/appearance.
Additionally, the following flags are available that provide extra hardening but may cause breakage or usability issues:
chrome://flags/#show-punycode-domainschrome://flags/#clear-cross-origin-referrers
Other flags are also provided for compatibility should you experience an issue related to some of the hardening enabled by default. For example, the default pop-up blocker is very strict, it may optionally be disabled chrome://flags/#strict-popup-blocking to improve usability.
Trivalent comes by default with content filtering enabled using chromium's internal subresource filter. The lists used for content filtering can be found in the trivalent-subresource-filter repository.
If you want to contribute to the subresource filter, example suggesting a new list, visit here.
Follow the contributing documentation, and make sure to respect the CoC.