Helium

Keep Chromium web compatibility while adopting ungoogled-chromium's reduced-Google baseline

Helium is not a browser engine rebuilt from scratch. It layers substantial project-specific patches on ungoogled-chromium, retaining Chromium's web compatibility and extension ecosystem while adopting a privacy posture different from stock Chromium and Chrome.

The README also credits patches from Inox, Debian, Bromite, Iridium Browser, and Brave. Release 0.17.1 updates both Chromium and the ungoogled-chromium base to the 153.0.8010.47 generation.

Sources: [2][3]

Integrate uBlock Origin as a browser component instead of treating ad blocking as an after-install step

The 0.17.1 dependency manifest pulls uBlock Origin 1.74.0-2 from imputnet/uBlock into third_party/ublock. Helium's patch set installs and configures uBlock as a browser component rather than relying only on users to add an extension later.

Release 0.17.1 also adds CNAME uncloaking support for the bundled uBlock component, showing that ad blocking is maintained as part of the browser distribution.

Sources: [4][3][5]

Publish the browser, platform packaging, and surrounding components as separate open-source repositories

The README lists separate macOS, Linux, and Windows packaging/tooling repositories alongside open-source Helium services, onboarding, and the project's uBlock fork.

Users can start at helium.computer, which selects a compatible platform download. The main repository's release has no operating-system binary assets because distribution is delegated to the platform repositories.

Sources: [2][3]

For people who want Chromium-family site compatibility with privacy defaults and ad blocking that differ from Chrome

Helium is easiest to compare when Chromium site and extension compatibility matters, but stock Chrome's Google integration is not the desired baseline. Its bundled ad-blocking architecture is also relevant when you want blocking to be part of the browser distribution rather than a separate extension-installation step.

It is still beta, so test it alongside an existing browser before making it your primary profile

The official README explicitly says Helium is currently beta and that unexpected issues may occur.

Browsers hold passwords, sessions, extensions, downloads, conferencing workflows, and other high-impact state. Keep an existing browser/profile available while validating the sites and workflows that matter to you.

Sources: [2]

Its Safe Browsing configuration is not identical to stock Chrome; evaluate privacy and security features separately

The ungoogled-chromium patch set included in 0.17.1 removes multiple Safe Browsing-related build dependencies, including chrome/browser/safe_browsing, advanced_protection, metrics_collector, and suspicious_site_warnings.

Reducing Google communication for privacy is not the same goal as phishing, malware, or dangerous-download protection. Do not assume stock Chrome's protection stack is present unchanged; verify the safeguards required by your threat model.

Sources: [6]

A Chromium fork depends on timely upstream tracking, so release freshness remains an operational security check

A browser exposes a large attack surface, making the lag between Chromium security fixes and downstream releases important. Version 0.17.1 tracks Chromium 153.0.8010.47 at publication time, but one matching release does not guarantee future update cadence.

After adoption, keep comparing Helium releases against Chromium stable and security updates, and retain a fallback browser if updates fall materially behind.

Sources: [3]

GitHub reports GPL-3.0, but imported code keeps its original licenses

Helium-specific code, patches, and other unique content are licensed under GPL-3.0. The README separately states that imported content retains its original license, citing unmodified ungoogled-chromium code under BSD 3-Clause as an example.

Treating every file in the repository as uniformly GPL-3.0 would therefore be inaccurate. Redistribution or derivative-browser work should preserve and review notices for Helium, Chromium, ungoogled-chromium, and imported patches.

Sources: [2][7]