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 8fcd0c7Oct 2, 2026, 04:08 AMpr/10631Back to current
Back to findings
Known issueKI-MENU-GUARD-BATCH-STALE-APPLY

Guard batches carry no generation token: a batch computed for the previous items publishes onto the new set

OpenOpenLow

Low-severity issue, currently open.

Description

The issue as recorded.

guardProc.onExited publishes collected output with no comparison against the items generation (providerProc has a revision check, guards do not). Overlapping ids keep the previous when:false on screen. When the newer script is EMPTY the deferred path clears the maps and returns without rebuildDisplay. The open menu then stays stuck on stale visibility (SX26/C09).

Affected requirements

The requirement(s) this issue violates — click through to the spec.

SW-REQ-260922-MQ37

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_reproducerprovesSW-REQ-260922-MQ37
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

Stale commits need a batch crossing an items reload; guards re-run on the next batch, which self-heals the visibility maps

The fix

tag each batch with an items serial and drop stale commits; rebuildDisplay after clearing the maps

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 1 requirements · 1 code files · 1 tests.

Requirements (1)
SW-REQ-260922-MQ37
Code files (1)
  • MenuModel.js
Tests (1)
  • menu-guards-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-MQ37
Implementing code (2)
  • shell/plugins/menu/MenuModel.js
    guardLine
  • shell/plugins/menu/MenuModel.js
    guardScript
Tests & evidence (1)
  • test/shell.d/menu-guards-test.sh

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-guard-batch-stale-apply.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