fast-cli
Test your download and upload speed using fast.com
Runssource: GitHubTypeScriptMITcommit 378e3ef9b7b1
TypeScript, MIT licensed. The project labels itself: cli app, command line tool, download speed, nodejs, npm package and speed test.
fast-cli runs. An Argusic agent installed it in 0.6 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install and tsc build succeed; CLI help and download speed measurement work end-to-end against fast.com; upload speed tests time out due to fast.com rate-limiting from the container IP
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 100 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.
- Upload tests (upload flag, json upload output) timeout at 90s with Protocol error (Runtime.callFunctionOn): Target closed10 minutes
- Node.js v18.19.1 does not meet >=20 requirement1 minute
- Install time
- under a minute
- Cold machine to finish
- 56 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- node distribution/cli.js --help returned correct usage (exit 0, 10 lines); node distribution/cli.js --json returned real speed data (downloadSpeed=3900 Mbps, latency=24ms, userLocation=Resita, RO); npm test (8 tests) = 6 passed, 2 failed
- Model tokens used
- 206,005
- Exact commit tested
- 378e3ef9b7b1
- 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.
/bin/sh -lc 'export PATH="/tmp/node-v20.18.3-linux-x64/bin:$PATH" && cd /work/repo && cat -n distri…
succeeded in 0ms:
1 #!/usr/bin/env node
2 import { jsx as _jsx } from "react/jsx-runtime";
3 import meow from 'meow';
4 import { render } from 'ink';
5 import Ui from './ui.js';
exec
/bin/sh -lc 'export PATH="/tmp/node-v20.18.3-linux-x64/bin:$PATH" && cd /work/repo && echo '"'ARGUS…
succeeded in 0ms:
tokens used
206,005Replay 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.6 minutes.
- Recovered from all 2 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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.6 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
Topics (from GitHub)
cli-appcommand-line-tooldownload-speednodejsnpm-packagespeed-test
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fast-cli)Questions
- Does fast-cli run?
- Yes. fast-cli runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test fast-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 378e3ef9b7b1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test fast-cli?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does fast-cli take to install?
- 0.6 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 fast-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing fast-cli?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for fast-cli?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.