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-2570GitHub issuePublicReceived

Consider using `curl` instead of `wget` for easier installation.

Reported by dylanbr · filed Aug 19, 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

Consider using `curl` instead of `wget` for easier installation.revision 1 · captured 2026-10-04 11:27 UTC via poll

I would submit a PR, but this is a change to the documentation and website, and I have not found public repositories for those.

Reasons why this is a good idea:

  • curl is included by default in Arch Linux because it's a dependency of pacman. This simplifies running archinstall at the beginning, with one less action needed.
  • The flags, for example curl -fsSL do not require an ambiguous character in the command. Unlike wget, which has a warning in the documentation (capital oh not zero in -q0-) because of this.
  • I feel that curl and wget are interchangeable for this purpose, so it makes sense to pick the one that causes less friction.

This would require these changes:

  1. Update the Getting Started guide:
  • Change wget -qO- https://omarchy.org/install | bash to curl -fsSL https://omarchy.org/install | bash
  • Remove (capital oh not zero in -q0-)
  1. Update https://omarchy.org/install to eval "$(curl -fsSL https://raw.githubusercontent.com/basecamp/omarchy/refs/heads/master/boot.sh)"
  2. Update https://omarchy.org/install-bare to
OMARCHY_BARE=true
eval "$(curl -fsSL https://raw.githubusercontent.com/basecamp/omarchy/refs/heads/master/boot.sh)"
View raw text
I would submit a PR, but this is a change to the documentation and website, and I have not found public repositories for those.

Reasons why this is a good idea:

- `curl` is included by default in Arch Linux because it's a dependency of `pacman`. This simplifies running `archinstall` at the beginning, with one less action needed.
- The flags, for example `curl -fsSL` do not require an ambiguous character in the command. Unlike `wget`, which has a warning in the documentation `(capital oh not zero in -q0-)` because of this.
- I feel that `curl` and `wget` are interchangeable for this purpose, so it makes sense to pick the one that causes less friction.

This would require these changes:

1. Update the `Getting Started` guide:
    - Change `wget -qO- https://omarchy.org/install | bash` to `curl -fsSL https://omarchy.org/install | bash`
    - Remove `(capital oh not zero in -q0-)`
2. Update `https://omarchy.org/install` to `eval "$(curl -fsSL https://raw.githubusercontent.com/basecamp/omarchy/refs/heads/master/boot.sh)"`
3. Update `https://omarchy.org/install-bare` to
```bash
OMARCHY_BARE=true
eval "$(curl -fsSL https://raw.githubusercontent.com/basecamp/omarchy/refs/heads/master/boot.sh)"
```

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.