Proof Portal
Omarchy
ProbeLabs74 findings · 88 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.
Remove > Theme shows on a stock install, where the remover has no theme to offer and the row only closes the menu
Low-severity issue, currently open.
Description
The issue as recorded.
Remove > Theme runs omarchy-theme-remove with no terminal (default/omarchy/omarchy-menu.jsonc:295). The script lists the directories under ~/.config/omarchy/themes that are not symlinks. With none, it prints "No extra themes installed." and exits 1. Nothing shows that line, so the row only closes the menu. On a stock install that folder is empty, so most users get this row. The list also includes dot-directories such as .git, which the script then refuses to remove. With only such a directory, the picker offers it, and picking it removes nothing. The Remove siblings hide behind a when: guard until there is something to remove; this row has no guard. Commit 5bc151f9 moved the remover to the menu picker and dropped the floating terminal that showed the line.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Correctness
- CVE surface
- None
Where it is
The code the issue lives in — peek the affected function inline to see it in context.
- omarchy menu: Remove > Theme (remove.theme row)
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
bash pocs/menu-remove-theme-guard.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
bash pocs/menu-remove-theme-guard.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Nothing breaks and no data changes: the row closes the menu and removes nothing. A user who has installed an extra theme gets the picker as before. omarchy theme remove in a terminal prints the message.
The fix
Hide the row until the remover has a theme it can remove. #7775 used this shape for Update > Extra Themes. A helper lists the removable themes, the directories that are not symlinks or dot-directories, and exits nonzero when there are none. The row's when: runs the helper. The remover reads its list from the same helper, so the row and the picker agree.
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
No authoredcode links reach these requirements in this historical reconstruction. Automatically derived code links aren't reconstructible for past runs, so implementing code may have existed without an authored trace.
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- pocs/menu-remove-theme-guard.sh
- proof/evidence/ki-menu-remove-theme-no-themes.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.