UptimeKit-CLI
A modern, cross‑platform CLI to monitor websites and APIs.
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 616373ef769d
JavaScript, MIT licensed. The project labels itself: cli, health check, nodejs, server monitoring, terminal, tui, uptime and uptime monitor.
UptimeKit-CLI runs, with stand-ins for the services it depends on. An Argusic agent installed it in 20 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The project builds, its 246-unit test suite passes 6/6 suites, and the CLI starts a background daemon, adds HTTP/DNS/SSL monitors, and renders a live TUI dashboard with real monitoring data (DNS resolution, SSL certificate validation, HTTP checks). The edit command was fixed to accept 0 retries. Node 22 is required.
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 92 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.
- Node.js 18 cannot parse `/v` regex flags used by [email protected], [email protected], [email protected] — all require Node >=203 minutes
- `edit` command's Zod schema had `retries: z.number().positive()` which rejects 0, the default retries value, breaking every edit operation3 minutes
- better-sqlite3 native addon segfaults under Node 22 because it was compiled for Node 18's ABI2 minutes
- Install time
- 20 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test with Node 22 exited 0, 246 passed, 24 snapshots, 6/6 suites; upkit --version printed '1.3.1'; upkit start launched daemon (PID confirmed via ps); upkit status rendered live TUI dashboard with real DNS UP (16ms, 100% uptime), real SSL VALID (37 days remaining), and HTTP DOWN (against local mock); heartbeats confirmed in DB (status up with 2ms latency against mock).
- Model tokens used
- 279,920
- Exact commit tested
- 616373ef769d
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exit=0 succeeded in 3866ms: Test Suites: 6 passed, 6 total Tests: 246 passed, 246 total Snapshots: 24 passed, 24 total Let me calculate the install minutes and do a clean stop. exec /bin/sh -lc 'cd /work/repo && PATH=/tmp/node20/node-v22.17.0-linux-x64/bin:$PATH /tmp/npm-prefix/bi… exited 1 in 1755ms: UptimeKit is not running. Please start it first using "upkit start". tokens used 279,920
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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 20 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
Of the 25 cli projects Argusic has installed and timed, UptimeKit-CLI was the 23rd fastest to reach a running state, and 23 of 25 reached one at all.
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 with mocks | 92.00 | 0.18 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 |
Topics (from GitHub)
clihealth-checknodejsserver-monitoringterminaltuiuptimeuptime-monitor
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/uptimekit-cli)Questions
- Does UptimeKit-CLI run?
- UptimeKit-CLI runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 20 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test UptimeKit-CLI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 616373ef769d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test UptimeKit-CLI?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does UptimeKit-CLI take to install?
- 20 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 UptimeKit-CLI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing UptimeKit-CLI?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does UptimeKit-CLI compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, UptimeKit-CLI was the 23rd fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for UptimeKit-CLI?
- 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.