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.
Comma in a binding description shifts every later CSV field: truncated label, wrong dispatcher, failed dispatch
Medium-severity issue, currently open.
Description
The issue as recorded.
dynamic_bindings prints cache rows as raw comma-joined CSV with no quoting (printf '%s,%s,%s,%s,%s', bin/omarchy-menu-keybindings:333). parse_binding_records sets FS=',' and takes action=$3/dispatcher=$4, so a description containing a comma ('Save, quit') shifts every later field. The menu shows the truncated label, and dispatch receives the literal string ' quit' as dispatcher and 'exec,alacritty' as arg. dispatch_binding treats that pair as an unknown dispatcher.
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-c06.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-jvx8-c06.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Shipped binding descriptions contain no commas; only user-authored descriptions with commas shift the CSV fields
The fix
Quote or escape the description field, or switch the internal record format to a separator descriptions cannot contain (TAB). Then parse with that separator end to end
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-csv-desc-comma.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.