wreq-js

HTTP client for Node.js with browser TLS fingerprint impersonation

Not yet testedsource: 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 has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
408
forks
17
open issues
3
watchers
7
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.

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.

  • wreq-python verified to run · Python · 8 shared topics
  • curl_cffi verified to run · Python · 6 shared topics
  • SeleniumBase verified to run · Python · 4 shared topics
  • camofox-browser verified to run · JavaScript · 4 shared topics
  • scrapy verified to run · Python · 2 shared topics
  • nginx verified to run · C · 2 shared topics

Run history

No recorded runs.

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 has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test wreq-js?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for wreq-js?
All 0 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