Proof Portal

Sign in
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 8418e7cOct 2, 2026, 03:04 AMquattro-proofBack to current
Back to findings
Known issueKI-MENU-PROVIDER-PARTIAL-COMMIT

Failed/killed providers commit their partial stdout and stay marked loaded; apps provider loads with no AppLibrary

OpenOpenLow

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.

SW-REQ-260922-EFNRSW-REQ-260922-Z680

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

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 reproducedprofileknown_issue_reproducer
Reproducer test
Run it yourself
pocs/menu-qml-static.sh
Covers (2)
Last run Sep 30, 2026, 11:02 PM

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.

Tracing blast radius…

Touch this finding and you re-check 2 requirements · 2 code files · 2 tests.

Requirements (2)
SW-REQ-260922-EFNRSW-REQ-260922-Z680
Code files (2)
  • Menu.qml
  • MenuModel.js
Tests (2)
  • 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.

SW-REQ-260922-EFNR
Implementing code (6)
  • shell/plugins/menu/Menu.qml
    disarmPointer
  • shell/plugins/menu/Menu.qml
    loadProvidersForSearch
  • shell/plugins/menu/Menu.qml
    mergeProviderRows
  • shell/plugins/menu/Menu.qml
    startNextProvider
  • shell/plugins/menu/Menu.qml
    startProviderForMenu
  • shell/plugins/menu/MenuModel.js
    swapProviderRows
Tests & evidence (2)
  • test/node/menumodel-replay.test.mjs
  • test/shell.d/menu-test.sh
SW-REQ-260922-Z680
Implementing code (4)
  • shell/plugins/menu/Menu.qml
    mergeProviderRows
  • shell/plugins/menu/Menu.qml
    slugify
  • shell/plugins/menu/MenuModel.js
    mergeAppRows
  • shell/plugins/menu/MenuModel.js
    swapProviderRows
Tests & evidence (2)
  • test/node/menumodel-replay.test.mjs
  • test/shell.d/menu-test.sh
Proof obligations (1)
atomicity

Operation either fully completes or has no effect.

  • ✓negative (required) — test/shell.d/menu-test.sh:921
  • ✓nominal (required) — test/shell.d/menu-test.sh:911

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.

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