Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
omarchy pacman repository
Reported by RaphaelKimmig · filed Aug 14, 2025Closed upstream on 2025-08-31 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
I think we should set up a pacman repository for all packages that are required by omarchy.
Relying on the AUR for prototyping this project was a great decision.
Now that this is moving towards becoming a production setup for a lot of people, it would be a good time to re-consider the available options.
For one, the AUR comes with a big fat warning not to install anything from there without manually reviewing the relevant files.
This warning is there for a reason, but with the way omarchy is set up right now, it is really hard to do that.
I imagine a build pipeline (on github) where all the PKGBUILD changes would be reviewed and manually allowed through.
Some of us (omarchy users) already review their PKGBUILD changes anyway.
We could do that work once and have the whole community benefit from the increase in security.
It would also allow us to ship specific versions of packages that are critical for omarchy.
We could e.g. ship uwsm-omarchy and make sure to only update that once we've done sufficient testing with a newer version.
This would help with issues discussed here https://github.com/basecamp/omarchy/pull/753
I've looked into the required setup a bit, and I think the amount of work looks quite manageable.
I haven't set anything up yet (and I won't have time to do so in the next weeks),
but if there is interest in this I would really like to approach this.
Does anyone here have experience with setting up such a process? Opinions?
View raw text
I think we should set up a pacman repository for all packages that are required by omarchy. Relying on the AUR for prototyping this project was a great decision. Now that this is moving towards becoming a production setup for a lot of people, it would be a good time to re-consider the available options. For one, the AUR comes with a big fat warning not to install anything from there without manually reviewing the relevant files. This warning is there for a reason, but with the way omarchy is set up right now, it is really hard to do that. I imagine a build pipeline (on github) where all the PKGBUILD changes would be reviewed and manually allowed through. Some of us (omarchy users) already review their PKGBUILD changes anyway. We could do that work once and have the whole community benefit from the increase in security. It would also allow us to ship specific versions of packages that are critical for omarchy. We could e.g. ship `uwsm-omarchy` and make sure to only update that once we've done sufficient testing with a newer version. This would help with issues discussed here https://github.com/basecamp/omarchy/pull/753 I've looked into the required setup a bit, and I think the amount of work looks quite manageable. I haven't set anything up yet (and I won't have time to do so in the next weeks), but if there is interest in this I would really like to approach this. Does anyone here have experience with setting up such a process? Opinions?
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.