Proof Portal

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

Omarchy Documentation Website - Extremely slow on Edge

Reported by Pinox · filed Aug 24, 2026Closed upstream on 2026-10-09 by its own reporter Pinox. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Decided: Out of scope — decided by agents · verified 5 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 Documentation Website - Extremely slow on Edgerevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

AMD X7950 64GB RAM 32GB vram

What's wrong?

Just something I noticed when reading the Omarchy documentation.
Moving from page to page in the docs sometimes resulted in waiting up to 10s for new topic to load. This is on 500Mb fibre line. Definitely something wrong with the docs site.

Update: I notice this only on MS Edge , chrome and firefox is working fine.
I am using adblock in edge.
Edge error message below.

<img width="1394" height="163" alt="Image" src="https://github.com/user-attachments/assets/e3fb7d6f-ebcf-4d25-ad9f-d73ed1a8a35f" />

<img width="1093" height="268" alt="Image" src="https://github.com/user-attachments/assets/afc4460c-b4c9-4933-95bb-26250993f3bc" />

<img width="761" height="56" alt="Image" src="https://github.com/user-attachments/assets/fbf9ac0c-78e5-42e4-8f1f-3444a6575022" />

<img width="747" height="74" alt="Image" src="https://github.com/user-attachments/assets/f3ef1bcb-d1e7-4ada-b58b-e44fcc11d422" />

Couple of likely solutions:

Scripts not async and blocking UI thread - Make sure the <script> tag loading this file includes the defer or async attribute:
<script defer data-domain="yourdomain" src="https://plausible.io/js/script.js"></script>

or put plausible.io - put it behind api endpoint to ensure adblocker do not block

The window.fetch Call Lacks a Timeout (c() Function)

`function c(t,n,e){
window.fetch&&fetch(t,{
method:"POST",
headers:{"Content-Type":"text/plain"},
keepalive:!0,
body:JSON.stringify(n)
})
.then(function(t){e&&e.callback&&e.callback({status:t.status})})
.catch(function(t){e&&e.callback&&e.callback({error:t})})
}`

If the HTML element containing this script does not have the defer or async attribute, the browser pauses HTML parsing, forces a synchronous layout calculation (layout thrashing/reflow) to measure the document height, and freezes thread execution until done.

e = f(); // Calls document.documentElement.scrollHeight / offsetHeight / clientHeight
i = h(); // Calls window.innerHeight / scrollY
new ResizeObserver(function(){ e = f() }).observe(document.documentElement);

View raw text
### System details

AMD X7950 64GB RAM 32GB vram

### What's wrong?

Just something I noticed when reading the Omarchy documentation.
Moving from page to page in the docs sometimes resulted in waiting up to 10s for new topic to load. This is on 500Mb fibre line. Definitely something wrong with the docs site. 

Update: I notice this only on MS Edge , chrome and firefox is working fine.
I am using adblock in edge.
Edge error message below. 


<img width="1394" height="163" alt="Image" src="https://github.com/user-attachments/assets/e3fb7d6f-ebcf-4d25-ad9f-d73ed1a8a35f" />


<img width="1093" height="268" alt="Image" src="https://github.com/user-attachments/assets/afc4460c-b4c9-4933-95bb-26250993f3bc" />

<img width="761" height="56" alt="Image" src="https://github.com/user-attachments/assets/fbf9ac0c-78e5-42e4-8f1f-3444a6575022" />

<img width="747" height="74" alt="Image" src="https://github.com/user-attachments/assets/f3ef1bcb-d1e7-4ada-b58b-e44fcc11d422" />


Couple of likely solutions:

Scripts not async and blocking UI thread  - Make sure the <script> tag loading this file includes the defer or async attribute:
<script defer data-domain="yourdomain" src="https://plausible.io/js/script.js"></script>

or put plausible.io - put it behind api endpoint to ensure adblocker do not block

The window.fetch Call Lacks a Timeout (c() Function)

`function c(t,n,e){
  window.fetch&&fetch(t,{
    method:"POST",
    headers:{"Content-Type":"text/plain"},
    keepalive:!0,
    body:JSON.stringify(n)
  })
  .then(function(t){e&&e.callback&&e.callback({status:t.status})})
  .catch(function(t){e&&e.callback&&e.callback({error:t})})
}`



If the HTML element containing this script does not have the defer or async attribute, the browser pauses HTML parsing, forces a synchronous layout calculation (layout thrashing/reflow) to measure the document height, and freezes thread execution until done.

e = f(); // Calls document.documentElement.scrollHeight / offsetHeight / clientHeight
i = h(); // Calls window.innerHeight / scrollY
new ResizeObserver(function(){ e = f() }).observe(document.documentElement);








  • e3fb7d6f-ebcf-4d25-ad9f-d73ed1a8a35f
  • afc4460c-b4c9-4933-95bb-26250993f3bc
  • fbf9ac0c-78e5-42e4-8f1f-3444a6575022
  • f3ef1bcb-d1e7-4ada-b58b-e44fcc11d422

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 08:37 UTC