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-369GitHub issuePublicDecided· Out of scope

Package repository metadata makes update download progress exceed 100%

Reported by MartinBoeckling · filed Sep 18, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Package repository metadata makes update download progress exceed 100%revision 1 · captured 2026-09-28 21:23 UTC via poll

Summary

omarchy update showed package download progress beyond 100% because the sizes advertised by the Omarchy repository did not match the actual package archive sizes.

Steps to reproduce

  1. Run omarchy update on Omarchy 4.0.3-1.
  2. Accept the available updates.
  3. Observe the total download counter while downloading the Omarchy-repository packages.

Expected behavior

The repository metadata's download sizes should match the archives, and the total progress should finish at 100%.

Actual behavior

Pacman listed a total download size of 555.76 MiB, but showed 637.0 MiB transferred before completion, so total progress passed 100%.

The affected package-list sizes shown before download were:

  • 1password: 161.47 MiB
  • omarchy: 76.99 MiB
  • openai-codex-desktop: 317.31 MiB

The actual completed archive sizes left in /var/cache/pacman/pkg were:

  • 1password-8.12.36-2-x86_64.pkg.tar.zst: 203,694,727 bytes
  • omarchy-4.0.4-1-x86_64.pkg.tar.zst: 120,288,145 bytes
  • openai-codex-desktop-26.911.61220-1-x86_64.pkg.tar.zst: 378,326,325 bytes

The update completed and all packages installed successfully, so this appears to be incorrect/stale DownloadSize data in the Omarchy package repository rather than an integrity failure.

Environment

  • Omarchy: 4.0.4-1 after the update (4.0.3-1 before it)
  • Screenshot attached separately
View raw text
## Summary

`omarchy update` showed package download progress beyond 100% because the sizes advertised by the Omarchy repository did not match the actual package archive sizes.

## Steps to reproduce

1. Run `omarchy update` on Omarchy 4.0.3-1.
2. Accept the available updates.
3. Observe the total download counter while downloading the Omarchy-repository packages.

## Expected behavior

The repository metadata's download sizes should match the archives, and the total progress should finish at 100%.

## Actual behavior

Pacman listed a total download size of **555.76 MiB**, but showed **637.0 MiB** transferred before completion, so total progress passed 100%.

The affected package-list sizes shown before download were:

- `1password`: 161.47 MiB
- `omarchy`: 76.99 MiB
- `openai-codex-desktop`: 317.31 MiB

The actual completed archive sizes left in `/var/cache/pacman/pkg` were:

- `1password-8.12.36-2-x86_64.pkg.tar.zst`: 203,694,727 bytes
- `omarchy-4.0.4-1-x86_64.pkg.tar.zst`: 120,288,145 bytes
- `openai-codex-desktop-26.911.61220-1-x86_64.pkg.tar.zst`: 378,326,325 bytes

The update completed and all packages installed successfully, so this appears to be incorrect/stale `DownloadSize` data in the Omarchy package repository rather than an integrity failure.

## Environment

- Omarchy: 4.0.4-1 after the update (4.0.3-1 before it)
- Screenshot attached separately

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 15:21 UTC