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.
parse_keycodes rewrites code:N/mouse:N tokens anywhere in a record, corrupting descriptions and commands
Medium-severity issue, currently open.
Description
The issue as recorded.
parse_keycodes' awk matches /code:([0-9]+)/ and /mouse:([0-9]+)/ against the whole comma-joined record and sub() rewrites the first occurrence (bin/omarchy-menu-keybindings:54-63) - not just the key field. A description like 'Count code:10 items' renders as 'Count 1 items'; a command like 'echo code:20' becomes 'echo MINUS'. 'notify-send mouse:272' becomes 'notify-send LEFT MOUSE BUTTON'. Real code: keys only survive because they happen to be the first match.
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.
./pocs/crs-260930-jvx8-c05.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-jvx8-c05.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Corruption needs code:N or mouse:N text inside a description or command; shipped binds keep such tokens in the key field only
The fix
Confine the substitution to the key field: apply match/sub per CSV field instead of on $0, rewriting only field 2
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.
Touch this finding and you re-check 1 requirements · 1 code files · 1 tests.
- omarchy-menu-keybindings
- keybindings-menu-test.sh
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.
- proof/evidence/ki-menu-keybindings-code-rewrite-overreach.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.