Proof Portal
Omarchy
ProbeLabs73 findings · 87 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.
Failed/killed providers commit their partial stdout and stay marked loaded; apps provider loads with no AppLibrary
Low-severity issue, currently open.
Description
The issue as recorded.
providerProc.onExited merges collected stdout whenever the revision matches, with no exitCode/exitStatus check. The guardProc beside it does check (asymmetry in the same file, anchors PRV1). A failed script therefore replaces a good row set with a partial read. The code commits providersLoaded BEFORE the process proves itself (PRV2) and never clears it on failure. The submenu therefore stays stuck until a full source rebuild. The apps branch marks providersLoaded unconditionally even when appLibrary is null and mergeAppRows returns empty (PRV3), leaving an empty Apps menu with no retry.
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_reproducerpocs/menu-qml-static.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
pocs/menu-qml-static.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
A failed provider leaves partial rows until the next successful run; static menu entries remain available throughout
The fix
check exitCode/exitStatus before merging (keep last good rows otherwise), set providersLoaded only on success, and re-run mergeAppRows when appLibrary appears
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 2 requirements · 2 code files · 2 tests.
- Menu.qml
- MenuModel.js
- menumodel-replay.test.mjs
- 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.
- pocs/menu-qml-static.sh
- proof/evidence/ki-menu-provider-partial-commit.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.