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 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The project builds with tsc, the CLI prints the --help output correctly, and all 8 test cases pass when run one at a time against real fast.com, including download/upload speed measurement, JSON output, verbose output with latency/client/server info, and non-TTY piped output.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
2
last tested
stars
2,897
forks
124
open issues
0
watchers
26
size
1 MB
created
last push

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.

Time lost to each failure while testing fast-cli, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18.19.1 installed, but project requires >=20. The tsc build and runtime crash with SyntaxError on /v regex flag0.5 minutes
  • Tests time out when running together via npm test (6 real Chrome browsers competing for resources)
Install time
1 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
NODE_OPTIONS='--import=tsx/esm' npx ava test.tsx -m <pattern> --timeout=10m passed all 8 tests individually (default, non-tty output, json output, upload flag, json upload output, verbose flag, help output, verbose flag in help)
Model tokens used
53,102
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.

The `npm test` command runs all 8 tests concurrently. The 6 tests that launch real Chrome instances…
**Issue #3: `npm test` needs Node 20 in PATH**
The `npm test` script uses `NODE_OPTIONS='--import=tsx/esm'` but relies on the system `node` being …
tokens used
53,102
Here's the final status.
**Issue #1: Node.js version too old (18.x vs required >=20)**
The system had Node 18.19.1; the project requires >=20. Fixed by downloading Node 20.10.0 prebuilt …
**Issue #2: Tests time out when run in parallel (resource contention)**
The `npm test` command runs all 8 tests concurrently. The 6 tests that launch real Chrome instances…
**Issue #3: `npm test` needs Node 20 in PATH**
The `npm test` script uses `NODE_OPTIONS='--import=tsx/esm'` but relies on the system `node` being …

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 1 minute, faster than the median of the 3 comparable projects Argusic has measured.
  • 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.
  • Measured 2 times, so the result is not a one-off.

Of the 4 cli-app projects Argusic has installed and timed, fast-cli was the 1st fastest to reach a running state, and 3 of 4 reached one at all.

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 1 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.08
Argusic Runner1/3Runs100.000.32

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.

[![Tested by Argusic](https://argusic.com/badge/fast-cli.svg)](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. 2 attempts are 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.08: 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?
1 minute 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.
How does fast-cli compare with the alternatives?
Of the 4 cli-app projects Argusic has installed and timed, fast-cli was the 1st fastest to reach a running state, and 3 of 4 reached one at all.
Where is the evidence for fast-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.

Discussion