node-request-retry
:guardsman: Wrap NodeJS request module to retry http requests in case of errors
Runssource: GitHubhomepageJavaScriptMITcommit 9d61cb22310b
JavaScript, MIT licensed. The project labels itself: http client, http requests and requests.
node-request-retry runs. An Argusic agent installed it in 1 minute and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completed, the mocha suite ran 61 passing tests including a 100%-coverage run, and a local smoke test observed a real HTTP 500 followed by an automatic retry that returned 200 with attempts: 2.
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.
- npm install printed EBADENGINE warning for transitive dep [email protected] (requires node >=20, container has node 18.19.1); install still completed1 minute
- npm install audit reported 19 vulnerabilities (8 high, 1 critical) in the dependency tree1 minute
- npm run test-coverage printed a Browserslist stale caniuse-lite cache notice1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- node /tmp/smoke.js against a local http server returned 'err: null statusCode: 200 attempts: 2 serverCalls: 2 exit=0', proving a 500-on-first-attempt request was retried and succeeded on attempt 2
- Model tokens used
- 65,306
- Exact commit tested
- 9d61cb22310b
- 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.
lcov.info coverage dir exists exec /bin/sh -lc 'cd /work/repo && git check-ignore coverage && echo "coverage is git-ignored" ; found=0… succeeded in 0ms: coverage coverage is git-ignored 2 All verification is complete and the git working tree is clean (the `coverage/` output is git-ignor… tokens used 65,306 All verification is complete and the git working tree is clean (the `coverage/` output is git-ignor…
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 4 comparable projects Argusic has measured.
- Recovered from all 3 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.
Of the 5 http-client projects Argusic has installed and timed, node-request-retry was the 1st fastest to reach a running state, and 4 of 5 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/node-request-retry)Questions
- Does node-request-retry run?
- Yes. node-request-retry runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test node-request-retry?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9d61cb22310b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test node-request-retry?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does node-request-retry 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 node-request-retry need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing node-request-retry?
- 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 node-request-retry compare with the alternatives?
- Of the 5 http-client projects Argusic has installed and timed, node-request-retry was the 1st fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for node-request-retry?
- 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.