Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-162GitHub issuePublicDecided· Out of scope

Chromium ships with upstream privacy defaults: search suggestions, prefetch, third-party cookies, WebRTC local addresses

Reported by brightwalker25 · filed Sep 23, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Chromium ships with upstream privacy defaults: search suggestions, prefetch, third-party cookies, WebRTC local addressesrevision 1 · captured 2026-09-28 21:23 UTC via poll

Omarchy version: 4.0.4

Chromium is the default browser, and the only managed policy Omarchy writes is /etc/chromium/policies/managed/color.json (from install/helpers/browser-policy.sh). Everything else is Chromium's upstream default, which for a privacy-conscious default setup means:

  • SearchSuggestEnabled: every keystroke in the address bar is sent to the default search engine before Enter is pressed
  • NetworkPredictionOptions: pages and DNS are fetched ahead of clicks
  • third-party cookies allowed, and the Privacy Sandbox ad APIs (Topics, site-suggested ads, ad measurement) on
  • WebRtcIPHandling: WebRTC can expose local network addresses to sites
  • AlternateErrorPagesEnabled and SpellCheckServiceEnabled: mistyped addresses and spelling go to Google services

Suggested fix: ship a second root-owned policy file next to color.json with those set to their private values (SearchSuggestEnabled: false, NetworkPredictionOptions: 2, BlockThirdPartyCookies: true, WebRtcIPHandling: "default_public_interface_only", the three PrivacySandbox* keys false, AlternateErrorPagesEnabled: false, SpellCheckServiceEnabled: false). None of them touch security updates, Safe Browsing or the component updater, and the visible cost is the suggestion dropdown.

View raw text
**Omarchy version:** 4.0.4

Chromium is the default browser, and the only managed policy Omarchy writes is `/etc/chromium/policies/managed/color.json` (from `install/helpers/browser-policy.sh`). Everything else is Chromium's upstream default, which for a privacy-conscious default setup means:

- `SearchSuggestEnabled`: every keystroke in the address bar is sent to the default search engine before Enter is pressed
- `NetworkPredictionOptions`: pages and DNS are fetched ahead of clicks
- third-party cookies allowed, and the Privacy Sandbox ad APIs (Topics, site-suggested ads, ad measurement) on
- `WebRtcIPHandling`: WebRTC can expose local network addresses to sites
- `AlternateErrorPagesEnabled` and `SpellCheckServiceEnabled`: mistyped addresses and spelling go to Google services

**Suggested fix:** ship a second root-owned policy file next to `color.json` with those set to their private values (`SearchSuggestEnabled: false`, `NetworkPredictionOptions: 2`, `BlockThirdPartyCookies: true`, `WebRtcIPHandling: "default_public_interface_only"`, the three `PrivacySandbox*` keys false, `AlternateErrorPagesEnabled: false`, `SpellCheckServiceEnabled: false`). None of them touch security updates, Safe Browsing or the component updater, and the visible cost is the suggestion dropdown.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 19:35 UTC