Yes. got runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test got?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit e1d87d2ced01. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test got?

The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does got take to install?

25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing got?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for got?

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.

got

🌐 Human-friendly and powerful HTTP request library for Node.js

Runssource: GitHubTypeScriptMITcommit e1d87d2ced01

TypeScript, MIT licensed. The project labels itself: http, http client, http request, https, nodejs and npm package.

got runs. An Argusic agent installed it in 25 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Got v16.0.0 installs, builds with tsc, and 1619+ ava tests pass across 33 test files with 5 skipped. Only 1 pre-existing container-network test quirk in test/timings.ts (resolver not invoked for localhost lookup). The HTTP client handles basic GET, POST with JSON, and streaming responses correctly against a real server.
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 60 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 60 / 100
cost of the verifying run: $0.19 (measured)
recorded runs: 2
last tested: 2026-09-28
stars: 14,949
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. 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 got, 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.

System Node.js v18 does not satisfy engine requirement >=225 minutes
Initial Node.js v22.0.0 too old for dnsOrder 'ipv6first' and ALPN callback APIs5 minutes
Test server binds to 0.0.0.0; direct connection fails with EADDRNOTAVAIL in Docker container5 minutes
1 pre-existing test failure in test/timings.ts - 'cached DNS lookups reuse resolved addresses in timing requests'5 minutes
npm install warnings about unsupported engines (node versions) for several devDependencies1 minute

Install time: 25 minutes
Cold machine to finish: 45 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: npm test runs xo lint (29 warnings, 0 errors), tsc --noEmit (passes), and ava test suite; all 33 test files pass individually (abort:37, agent:9, arguments:118, cache:68+2skip, cookies:46, create:77, diagnostics-channel:29, dns-cache-fallback:4, dns-cache-integration:7, dns-cache:58, early-307-redirects:15, encoding:2, error:50, get-unix-socket-path:6, gzip:20, headers:44, helpers:1, hooks:198, http:39+2skip, https:130, infinite-loop:1, merge-instances:11, no-body-status-codes:36, normalize-arguments:70, pagination-options:40, pagination:151, parse-link-header:25, post:55, progress:34, promise:44, redirects:179, request-timeout:18, response-parse:115, retry-attempt-count:17, retry:109, stream:99+1skip, timed-out:14, timeout:94, timer-utils:23, unix-socket:22, weakable-map:1, zstd:8). Manual smoke test with real HTTP server: got('GET') -> 200, got().json() -> {ok:true}, got.post({json}) -> {ok:true}, got.stream() -> decoded body.
Model tokens used: 269,577
Exact commit tested: e1d87d2ced01
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.

ff02::1  ip6-allnodes
ff02::2  ip6-allrouters
172.29.0.32  ad594a40dab3
ad594a40dab3
exec
/bin/sh -lc 'export PATH="/tmp/node-v22.23.3-linux-x64/bin:$PATH" && cd /work/repo && duration_min=…
 succeeded in 0ms:
duration min estimate: ~20
Here's the final result:
tokens used
269,577
Here's the final result:

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 25 minutes.
Recovered from all 5 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.

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	100.00	0.19	2026-09-28 09:02 UTC
Argusic Runner	1/3	Did not run	20.00	0.17	2026-09-28 08:16 UTC

Topics (from GitHub)

http http-client http-request https nodejs npm-package

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/got.svg)](https://argusic.com/subject/got)

Questions

Does got run?: Yes. got runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test got?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit e1d87d2ced01. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test got?: The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does got take to install?: 25 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 got need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing got?: 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for got?: 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.

got