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 1e19056Oct 2, 2026, 06:55 AMpr/13968Back to current
Back to findings
Known issueKI-MENU-OPEN-NULL-PAYLOAD

open() throws on a JSON null payload: parse succeeds, the catch does not run, the property read throws

OpenOpenLow

Low-severity issue, currently open.

Description

The issue as recorded.

JSON.parse('null') returns null without throwing, so the try/catch in open() does not cover the dereference. payload.fontFamily throws TypeError and no mode dispatch runs, so nothing answers the summon lifecycle (anchors; SX26/C05 reproduced the null hole).

Affected requirements

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

SW-REQ-260922-50RE

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-50RE
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 null payload only comes from a broken summoner; in-tree callers always send a JSON object with a mode field

The fix

guard the parse result with an object type check before dereferencing

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-50RE
Code files (1)
  • Menu.qml
Tests (1)
  • menu-compositor-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-50RE
Implementing code (5)
  • shell/plugins/menu/Menu.qml
  • shell/plugins/menu/Menu.qml
    disarmPointer
  • shell/plugins/menu/Menu.qml
    open
  • shell/plugins/menu/Menu.qml
    openDmenu
  • shell/plugins/menu/Menu.qml
    requestDeleteSelected
Tests & evidence (1)
  • test/shell.d/menu-compositor-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-open-null-payload.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