wreq-js

HTTP client for Node.js with browser TLS fingerprint impersonation

Runs with mockssource: GitHubTypeScriptMITcommit 3e5c4d4bde7a

TypeScript, MIT licensed. The project labels itself: anti detection, bot detection, cloudflare, cloudflare bypass, curl impersonate, fetch, fingerprint and http client.

wreq-js runs, with stand-ins for the services it depends on. An Argusic agent installed it in 27 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

wreq-js v3.2.0 is installed and working on x86_64 Ubuntu 24.04 with Node.js v22.23.4, the TypeScript build completes, the native Rust binding (prebuilt) loads correctly, and the test suite passes 195/200 tests against a local HTTP/HTTPS/WebSocket test 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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.18 (measured)
recorded runs
1
last tested
stars
464
forks
20
open issues
10
watchers
8
size
2 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 wreq-js, 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.

  • Rust build from source fails — btls-sys crate needs libclang for bindgen, and system has no libclang-dev. Downloaded libclang deb but still missing clang resource files for stddef.h15 minutes
  • Prebuilt binary missing setCookies (plural) — the Rust source exports fn set_cookies but the published binding predates that addition2 minutes
  • wreq Rust HTTP library drops non-UTF8 header byte sequences — test expects raw latin1 Location header bytes2 minutes
  • 5 session tests requiring native setCookies (sameSite validation, batch error rollback, expired cookie filtering) cannot run with JS polyfill2 minutes
  • Node.js 18 system-installed, need >=201 minute
  • No Rust toolchain1 minute
Install time
27 minutes
Cold machine to finish
28 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
npm run test:run exited 0, 195 passed, 5 skipped, 0 failed across 24 test suites (HTTP, WebSocket, sessions, emulation, TLS, etc.) using a local test server
Model tokens used
822,890
Exact commit tested
3e5c4d4bde7a
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.

# suites 24
# pass 195
# fail 0
# cancelled 0
# skipped 5
# todo 0
# duration_ms 3189.576871
EXIT_CODE: 0
All done. Here's the summary:
tokens used
822,890
All done. Here's the summary:

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

  • Installed in 27 minutes.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs with mocks92.000.18

Topics (from GitHub)

anti-detectionbot-detectioncloudflarecloudflare-bypasscurl-impersonatefetchfingerprinthttp-clienthttp2ja3ja4scrapingtlstls-fingerprinttypescriptweb-scraping

Embed the badge

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

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

Questions

Does wreq-js run?
wreq-js runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 27 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test wreq-js?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3e5c4d4bde7a. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test wreq-js?
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 wreq-js take to install?
27 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 wreq-js need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing wreq-js?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for wreq-js?
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.

Discussion