Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
A more verifiable default installation command?
Reported by pelephant2 · filed Aug 5, 2025Closed upstream on 2025-08-06 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Let me present ~three~ two options for the installation of Omarchy.
Option 1 (Current State)
wget -qO- https://omarchy.org/install | bashOption 2
wget -qO- https://github.com/basecamp/omarchy/blob/master/install.sh | bashAnother Option 2?
curl -fsSL https://github.com/basecamp/omarchy/blob/master/install.sh | shIt seems that option 1 is ultimately a black box (barring my access to omarchy.org), and option 2 is something I can go and verify myself on GitHub. Some early criticism I read about Omarchy amounted to, "I'm not doing option 1 on my PC!!" because it's unverifiable. Could this objection be overcome with an option 2?
Are either of my option 2s even technically correct, and is there a correct way to do option 2? Maybe the end user is more comfortable running an installation script from an auditable source, in this case the Omarchy GitHub repo.
View raw text
Let me present ~three~ two options for the installation of Omarchy. **Option 1 (Current State)** ``` wget -qO- https://omarchy.org/install | bash ``` **Option 2** ``` wget -qO- https://github.com/basecamp/omarchy/blob/master/install.sh | bash ``` **Another Option 2?** ``` curl -fsSL https://github.com/basecamp/omarchy/blob/master/install.sh | sh ``` It seems that option 1 is ultimately a black box (barring my access to `omarchy.org`), and option 2 is something I can go and verify myself on GitHub. Some early criticism I read about Omarchy amounted to, "I'm not doing option 1 on my PC!!" because it's unverifiable. Could this objection be overcome with an option 2? Are either of my option 2s even technically correct, and is there a correct way to do option 2? Maybe the end user is more comfortable running an installation script from an auditable source, in this case the Omarchy GitHub repo.
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.
No decision has been recorded yet.