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

omarchy-network-speedtest fails: fast.com API rejects the hardcoded token (403)

Reported by giuseppecipollone · filed Sep 10, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

omarchy-network-speedtest fails: fast.com API rejects the hardcoded token (403)revision 1 · captured 2026-09-28 21:23 UTC via poll

Description

The network speed test from the Wi-Fi panel never starts. The overlay opens, then immediately errors with "Failed to fetch speed test endpoints".

Expected

Speed test runs and shows live download/upload Mbps.

Actual

omarchy-network-speedtest down exits 1:
Failed to fetch speed test endpoints

The script hardcodes a fast.com token (/usr/bin/omarchy-network-speedtest:43):
fast_token="YXNkZmFzZGxmbnNkYWZoYXNkZmhrYWxm" # base64 -> "asdfasdlfnsdafhasdfhkalf"

curl against the resulting API URL returns HTTP 403 ("Not Available"), so .targets[] is empty and the script aborts before any traffic runs. The panel then shows the speed test as failed.

Steps to reproduce

  1. Click the network widget in the bar -> open panel -> "Speed Test"
  2. Observe overlay error instead of a measurement

(or from a terminal: omarchy-network-speedtest down)

System details

  • Omarchy: 4.0.3-1
  • Kernel: 7.2.3-arch1-3
  • CPU: Intel(R) Core(TM) Ultra 9 185H
  • GPU: Intel Meteor Lake-P [Intel Arc Graphics]

Proposed fix

Fetch the token dynamically from fast.com (it rotates) instead of hardcoding it, or switch the backend to endpoints that need no token, e.g. Cloudflare's speed test (https://speed.cloudflare.com/__down?bytes=N and /__up) which already measure fine and need no credentials.

View raw text
## Description
The network speed test from the Wi-Fi panel never starts. The overlay opens, then immediately errors with "Failed to fetch speed test endpoints".

## Expected
Speed test runs and shows live download/upload Mbps.

## Actual
`omarchy-network-speedtest down` exits 1:
  Failed to fetch speed test endpoints

The script hardcodes a fast.com token (/usr/bin/omarchy-network-speedtest:43):
  fast_token="YXNkZmFzZGxmbnNkYWZoYXNkZmhrYWxm"   # base64 -> "asdfasdlfnsdafhasdfhkalf"

`curl` against the resulting API URL returns HTTP 403 ("Not Available"), so `.targets[]` is empty and the script aborts before any traffic runs. The panel then shows the speed test as failed.

## Steps to reproduce
1. Click the network widget in the bar -> open panel -> "Speed Test"
2. Observe overlay error instead of a measurement
   (or from a terminal: `omarchy-network-speedtest down`)

## System details
- Omarchy: 4.0.3-1
- Kernel: 7.2.3-arch1-3
- CPU: Intel(R) Core(TM) Ultra 9 185H
- GPU: Intel Meteor Lake-P [Intel Arc Graphics]

## Proposed fix
Fetch the token dynamically from fast.com (it rotates) instead of hardcoding it, or switch the backend to endpoints that need no token, e.g. Cloudflare's speed test (https://speed.cloudflare.com/__down?bytes=N and /__up) which already measure fine and need no credentials.

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 11:27 UTC