statuspage
A simple, zero-dependency, pure js/html status page based on GitHub Pages and Actions.
Runssource: GitHubJavaScriptISCcommit 4edbee1a8c91
JavaScript, ISC licensed. The project labels itself: availability, availability monitor, statsig and status page.
statuspage runs. An Argusic agent installed it in 0 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Health check script curls 5 URLs and logs results; static server serves index.html, JS, CSS, SVG, config, and 5 log files with 200 status.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- under a minute
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- bash health-check.sh -> 5 URLs all success; python3 http.server -> all 6 static files returned HTTP 200
- Model tokens used
- 21,101
- Exact commit tested
- 4edbee1a8c91
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **Tests:** No test suite or package.json exists in this repo. - **Errors:** None encountered. 2026-09-19T02:03:04.533061Z ERROR codex_core::session: failed to record rollout items: thread 01a0b… tokens used 21,101 All checks passed with zero errors. Let me compile the final report. Here's the full summary: - **Install:** None needed — this is a pure static HTML/JS/CSS project with a shell script. No depe… - **Health check:** `bash health-check.sh` ran curl against all 5 URLs (google, hn, reddit, statsig… - **Static server:** `python3 -m http.server 8080` served all 6 asset files (index.html, index.js, … - **Tests:** No test suite or package.json exists in this repo. - **Errors:** None encountered.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed ISC, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.01 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/statuspage)Questions
- Does statuspage run?
- Yes. statuspage runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test statuspage?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4edbee1a8c91. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test statuspage?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does statuspage take to install?
- 0 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does statuspage need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing statuspage?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for statuspage?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.