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 a72e7f1Oct 2, 2026, 07:59 AMpr/6525Back to current
Back to findings
Known issueKI-MENU-GOBACK-ROOT-STRAND

goBack refuses to retrace while activeMenu is root, stranding navStack after a drill that landed on root

OpenOpenLow

Low-severity issue, currently open.

Description

The issue as recorded.

The route code rewrites a missing link target to root before pushing its source (Menu.qml:786-787). An explicit root link or a reload-forced root does the same. Then goBack's root early-return (801) never pops the stack and Back is a permanent no-op (SX26/C04).

Affected requirements

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

SW-REQ-260922-N3RM

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-N3RM
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

Back at root the menu keeps working; the stranded navStack entry only surfaces if the user drills down and retraces the same path

The fix

pop navStack in goBack even when activeMenu is root, or clear navStack when rewriting the target to root

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 · 2 tests.

Requirements (1)
SW-REQ-260922-N3RM
Code files (1)
  • Menu.qml
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-N3RM
Implementing code (3)
  • shell/plugins/menu/Menu.qml
    requestDeleteSelected
  • shell/plugins/menu/Menu.qml
    resolveRoute
  • shell/plugins/menu/Menu.qml
    runAction
Tests & evidence (2)
  • test/node/menumodel-replay.test.mjs
  • test/shell.d/menu-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-goback-root-strand.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