Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

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.

Inbox
ReportR-2549GitHub issuePublicReceived

Optional --noconfirm for AUR via prefs.conf and yay_helper

Reported by ttmachado · filed Aug 16, 2025Closed upstream on 2025-08-22 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Optional --noconfirm for AUR via prefs.conf and yay_helperrevision 1 · captured 2026-10-04 11:27 UTC via poll

Using --noconfirm for operations targeting AUR packages should not be encouraged. Diffs should be read and verified whenever there's a change in order to reduce the risk of a package take over or a maintainer acting maliciously. Currently, if this was the case with one of the existing AUR packages on a user's system, once he decided to update its installation through the Omarchy Menu, it would go through without any confirmation.

The default behavior should be to avoid --noconfirm, but this could go against what some users now expect. Therefore, I propose the following non-intrusive changes:

  1. Create a prefs file at ~/.config/hypr/prefs.conf that defines environment variables such as OMARCHY_YAY_NOCONFIRM, providing a central place for users to configure preferences.
  2. Create a yay_helper that wraps package installation, reads the environment variables from prefs.conf, and applies --noconfirm accordingly; replace scattered direct calls with this helper.
View raw text
Using `--noconfirm` for operations targeting AUR packages should not be encouraged. Diffs should be read and verified whenever there's a change in order to reduce the risk of a package take over or a maintainer acting maliciously. Currently, if this was the case with one of the existing AUR packages on a user's system, once he decided to update its installation through the Omarchy Menu, it would go through without any confirmation.

The default behavior should be to avoid `--noconfirm`, but this could go against what some users now expect. Therefore, I propose the following non-intrusive changes:

1. Create a prefs file at `~/.config/hypr/prefs.conf` that defines environment variables such as `OMARCHY_YAY_NOCONFIRM`, providing a central place for users to configure preferences.
2. Create a yay_helper that wraps package installation, reads the environment variables from `prefs.conf`, and applies `--noconfirm` accordingly; replace scattered direct calls with this helper.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.