← Home

reqwest

npm Repository Homepage

A wrapper for asynchronous http requests

71
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dedrvagg

Keywords

enderajaxxhrconnectionweb 2.0asyncsync

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff source-size-tripled AI (source-diff): Size increase from 11KB to 178KB is explained by addition of legitimate build tool dependencies (uglify-js, jshint, rimraf, gzip, sqwish, asciimo, colors) for this JS packager. ai
publish-pattern new-deps-added AI (publish-pattern): New deps (uglify-js, jshint, rimraf, gzip, sqwish, asciimo, colors) are all well-known, legitimate build tooling packages consistent with a JS packager tool. ai
source-diff large-new-source-files AI (source-diff): smoosh is a JS build/packaging tool; large number of source files reflects legitimate build tooling dependencies (uglify-js, jshint, etc.), not injected code. ai
email-domain unclaimed-email:ded AI (email-domain): Author field uses '@ded' as a social handle (Twitter/GitHub), not a real email address. 'ded' is not a valid TLD; this is a persistent false positive for this package. ai
phantom-deps phantom-dep:valentine AI (phantom-deps): valentine is used as an Ender.js build/bundle dependency by the same author (Dustin Diaz/@ded), not a direct require(). Expected pattern for this ecosystem. ai
npm-metadata bundled-binaries AI (npm-metadata): vendor/phantomjs is a well-known headless browser used for testing; explicitly excluded from spm distribution. Not a backdoor risk for this established package. ai
semgrep semgrep:child-process-import AI (semgrep): child_process is imported in make/tests.js (test/build tooling), not in runtime code. Expected for a build tool package. ai
semgrep semgrep:eval-usage AI (semgrep): eval() in reqwest.js is a legacy JSON.parse fallback pattern (JSON ? JSON.parse(r) : eval('(' + r + ')')), a well-known safe pattern for old browser compatibility. Not a supply-chain risk. ai
typosquat typosquat.levenshtein:request AI (typosquat): reqwest is a legitimate, intentionally named browser AJAX library by Dustin Diaz (ded), ~15 years old with 72 versions. Not a typosquat of 'request'. ai

Versions (showing 71 of 71)

Version Deps Published
2.0.5 0 / 8
2.0.4 0 / 8
2.0.3 0 / 8
2.0.2 0 / 8
2.0.1 0 / 8
2.0.0 0 / 8
1.1.6 0 / 8
1.1.5 0 / 8
1.1.4 0 / 8
1.1.3 0 / 8
1.1.2 0 / 8
1.1.0 0 / 8
1.0.2 0 / 8
1.0.1 0 / 8
0.9.7 0 / 8
0.9.6 0 / 8
0.9.5 0 / 8
0.9.4 0 / 8
0.9.3 0 / 8
0.9.2 0 / 8
0.9.1 0 / 8
0.9.0 0 / 7
0.8.2 0 / 7
0.8.1 0 / 7
0.8.0 0 / 7
0.7.3 0 / 7
0.7.2 0 / 7
0.7.1 0 / 7
0.7.0 0 / 7
0.6.5 0 / 7
0.6.4 0 / 6
0.6.2 0 / 6
0.6.1 0 / 6
0.6.0 0 / 6
0.5.1 0 / 6
0.5.0 0 / 5
0.4.5 0 / 5
0.4.3 0 / 5
0.4.2 0 / 5
0.4.1 0 / 5
0.4.0 0 / 5
0.3.3 0 / 6
0.3.2 0 / 6
0.3.1 0 / 6
0.3.0 0 / 6
0.2.8 0 / 6
0.2.7 0 / 6
0.2.5 0 / 6
0.2.4 0 / 5
0.2.3 0 / 5
0.2.2 0 / 5
0.2.1 0 / 5
0.2.0 1 / 5
0.1.9 1 / 5
0.1.8 1 / 5
0.1.7 1 / 5
0.1.6 1 / 5
0.1.5 1 / 5
0.1.4 1 / 5
0.1.3 1 / 5
0.1.2 1 / 0
0.1.1 1 / 0
0.0.9 0 / 0
0.0.8 0 / 0
0.0.7 0 / 0
0.0.6 0 / 0
0.0.5 0 / 0
0.0.4 0 / 0
0.0.3 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v0.9.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

2 findings
HIGH Unclaimed maintainer email domain: ded email-domain

Maintainer email '@ded' uses domain 'ded' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.