Proof Portal
Omarchy
ProbeLabsviewing a historical runA 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.
Failed jq payload build still execs the menu IPC with an empty payload and exits 0
Low-severity issue, currently open.
Description
The issue as recorded.
toggle and summon (bin/omarchy-menu:23,26) embed $(menu_payload ...) inside the exec with no status check. When jq fails, the substitution is empty, the script still execs omarchy-shell shell toggle/summon omarchy.menu '' and exits 0. A broken payload builder presents as a successful menu open that silently does nothing (the plugin receives an empty payload).
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
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_reproducer./pocs/crs-260930-3vzg-menu.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-3vzg-menu.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
jq is a core dependency; failure is rare
The fix
Build the payload first with a status check (payload=$(menu_payload ...) || exit 1) and refuse to exec with an empty payload
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.
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.
- proof/evidence/ki-menu-cli-jq-fail-looks-success.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.