issue-status
A flexible, modern and blazingly fast ☄️ status page
Runssource: GitHubhomepageTypeScriptMITcommit 1c04c03128c1
TypeScript, MIT licensed. The project labels itself: incident management, issue status, status page and system monitoring.
issue-status runs. An Argusic agent installed it in 38 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The issue-status monorepo is fully functional: pnpm install succeeds, tests pass (1 passed, 1 skipped/todo), the issue-status package builds via Vite, both CLIs build via tsdown, the example status page app builds and serves correctly via dev/built modes, and the GitHub provider fetches real data from the public GitHub API without authentication.
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- dayjs ESM build has extensionless relative imports (e.g., import './constant' instead of './constant.js') that fail under Node's native ESM loader. When vite.config.ts uses tsx's tsImport to load the user's config file, Node loads dayjs/esm which fails with ERR_MODULE_NOT_FOUND.10 minutes
- [email protected] fails to load its config because it defaults to `unrun` as the config loader, which is not installed. Error: Failed to import module "unrun". Please ensure it is installed.5 minutes
- vitest cannot start because vite.config.ts throws 'issue-status.config.ts not found' when CWD is the package directory without a config file.5 minutes
- Node v18 is too old for Vite 8 which requires ^20.19.0 || >=22.12.0. Also @clack/core needs styleText from node:util (Node 20.12+).3 minutes
- Install time
- 38 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- Model tokens used
- 786,709
- Exact commit tested
- 1c04c03128c1
- Container image
- sha256:4c3d41857be3
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
=== DONE === All good. Let me now compute the time. I started around and it's been about 20 minutes. Let me writ… Let me check start time from the logs - the current date is 2026-09-03 and it's around 11:13 now. I… Total elapsed: ~38 minutes (let me check more exec /bin/sh -lc 'echo "Started at about 10:35 UTC, now is about 11:13 UTC"' in /work/repo succeeded in 0ms: Started at about 10:35 UTC, now is about 11:13 UTC About 38 minutes total. Well within the 45 minute limit. tokens used 786,709 About 38 minutes total. Well within the 45 minute limit.
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 38 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, 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.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.06 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.46 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/issue-status)Questions
- Does issue-status run?
- Yes. issue-status runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test issue-status?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1c04c03128c1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test issue-status?
- The run that produced this verdict cost $0.46: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does issue-status take to install?
- 38 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 issue-status need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing issue-status?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for issue-status?
- 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.