Proof Portal

Project overview

Omarchy

ProbeLabsviewing a historical run

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.

Viewing historical run 8b74946Oct 3, 2026, 10:15 PMpr/14153Back to current
Back to findings
Known issueKI-MENU-REMOVE-THEME-NO-THEMES

Remove > Theme shows on a stock install, where the remover has no theme to offer and the row only closes the menu

FixedFixedLow

This defect has been fixed and verified.

Closure: Fix witnessed

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).

LowRated severity — the impact if this issue is exploited or hit.
why this rating
Risk-rated
risk area
Correctness
Security classification
Not a security surface
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.

Known issue not reproducedprofileknown_issue_reproducer
Reproducer test
Run it yourself
bash test/shell.d/menu-guards-test.sh
Covers (2)
Last run Oct 3, 2026, 8:54 PM

Reproduction steps

Technical steps for your engineers to confirm the issue by hand.

bash test/shell.d/menu-guards-test.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

Fixed by PR #14153 (omarchy-theme-removable), with SW-REQ-261003-390Z. It closes issue #14150. A new helper lists the themes the remover can remove: directories under ~/.config/omarchy/themes that are not symlinks or dot-directories. A themes folder that is itself a symlink offers nothing. The remove.theme row asks it as its when:, and the remover reads its list from it. So the row and the picker cannot disagree.

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.

Tracing blast radius…

Touch this finding and you re-check 9 requirements · 5 code files · 17 tests.

Code files (5)
  • omarchy-theme-removable
  • omarchy-theme-remove
  • omarchy-menu.jsonc
  • MenuModel.js
  • Menu.qml
Tests (17)
  • menu-guards-test.sh
  • guard-remove-theme-cloned.events
  • guard-remove-theme-copied.events
  • guard-remove-theme-dashed.events
  • guard-remove-theme-dotted.events
  • guard-remove-theme-empty.events
  • guard-remove-theme-filed.events
  • guard-remove-theme-folded.events
  • and 9 more

Per-requirement evidence

For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.

Tests & evidence (1)
  • test/shell.d/menu-guards-test.sh
Proof obligations (2)
error_handling

Behavior when operations fail or dependencies are unavailable.

  • ✓negative (required) — test/shell.d/menu-guards-test.sh:203
  • ✓nominal (required) — test/shell.d/menu-guards-test.sh:185
external_call_timeout_bounded

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

  • ✗nominal (required)
Implementing code (3)
  • bin/omarchy-theme-removable
  • bin/omarchy-theme-remove
  • default/omarchy/omarchy-menu.jsonc
    remove.theme
Tests & evidence (14)
  • test/bdiff/corpus/lifecycle/guard-remove-theme-cloned.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-copied.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-dashed.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-dotted.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-empty.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-filed.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-folded.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-hidden.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-linked.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-missing.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-mixed.events
  • test/bdiff/corpus/lifecycle/guard-remove-theme-worktree.events
  • test/bdiff/harness.mjs
  • test/shell.d/menu-guards-test.sh

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.

Sign in to discuss this with the proof team.Sign in