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.
Add better password enforcement to the installer
Reported by ryanrhughes · filed Oct 27, 2025Closed upstream on 2025-11-02 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
During the install, the configurator will allow you to set any password at all, including "a". While I don't think we should go prescribing crazy constraints, I do think it may be nice to add a simple suggestion to this area, as well as perhaps an alert for second confirmation if the user provides a password that is too simple.
This way, if I try to set the password "111", I get a prompt alerting me that this is a horrible password and I should really reconsider. But if I choose yes, proceed anyway with the remainder of the install. Otherwise, loop back to the password prompt.
View raw text
During the install, the [configurator](https://github.com/omacom-io/omarchy-iso/blob/main/configs/airootfs/root/configurator) will allow you to set any password at all, including "a". While I don't think we should go prescribing crazy constraints, I do think it may be nice to add a simple suggestion to this area, as well as perhaps an alert for second confirmation if the user provides a password that is too simple. This way, if I try to set the password "111", I get a prompt alerting me that this is a horrible password and I should really reconsider. But if I choose yes, proceed anyway with the remainder of the install. Otherwise, loop back to the password prompt.
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.