fettle
Free GitHub-powered beautiful status page utilizing GitHub Pages, Actions, and Issues for real-time updates and incident management. Make sure to share love by giving it a star.🌟
Runssource: GitHubhomepageTypeScriptApache-2.0commit 0622c94851f7
TypeScript, Apache-2.0 licensed. The project labels itself: monitoring, nextjs, status and status page.
fettle runs. An Argusic agent installed it in 10 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
Fettle installs, builds, and exports cleanly (next.config.js patched for image optimization); the production server and the exported static site both serve HTTP 200, and a real headless-browser load of the exported page fetched live GitHub data and showed all systems operational with both services and incidents rendered.
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 91 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.
- next export failed: 'Image Optimization using Next.js' default loader is not compatible with next export' (blocks the GitHub Pages deployment path used by .github/workflows/pages.yml)5 minutes
- scripts/health-check.sh ended with 'fatal: You are not currently on a branch' during git push1 minute
- Install time
- 10 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- npm run build exited 0 (compiled, 3 static pages); npm run start -p 3457 answered HTTP 200; a headless Chromium (Playwright) run against the exported site (python3 -m http.server serving out/) returned title 'System Status', rendered 'All System Operational', Google and Facebook service rows, and the 'Scheduled maintenance' incident, with 0 JS errors
- Model tokens used
- 127,125
- Exact commit tested
- 0622c94851f7
- 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.
exec /bin/sh -lc "cd /work/repo && git status --short && ls /tmp/e2e-final.mjs /tmp/fettle.png 2>/dev/nu… succeeded in 0ms: M next.config.js ?? out/ ?? package-lock.json /tmp/e2e-final.mjs /tmp/fettle.png 404.html _next error.svg favicon.ico grid.svg incident.svg index.html ss.png status urls.cfg vercel… deps clean: true tokens used 127,125
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 10 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Hit 2 errors during setup, 1 of which were not solved.
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 10 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 90.00 | 0.07 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fettle)Questions
- Does fettle run?
- Yes. fettle runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test fettle?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0622c94851f7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test fettle?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does fettle take to install?
- 10 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 fettle need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing fettle?
- 2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for fettle?
- 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.