superagent
elegant & feature rich browser / node HTTP with a fluent API
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): This is a very old package (5357 days) published long before Sigstore provenance existed on npm; absence of provenance is expected and not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:cookiejar | AI (dependencies): cookiejar is a long-standing, well-known dependency of superagent; its use is expected and stable across versions. | ai | |
| dependencies | unvetted-dep:formidable | AI (dependencies): formidable is a well-established multipart form parsing library; expected dependency for an HTTP client. Stable for this package. | ai | |
| dependencies | unvetted-dep:component-emitter | AI (dependencies): component-emitter is a classic, widely-used Node.js event emitter package; long-standing dependency of superagent. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Code comment documents legitimate use case (raw IP with Host header override); not malicious code execution. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 10.3.0 | 9 / 36 | |
| 10.2.2 | 9 / 36 | |
| 10.2.1 | 9 / 36 | |
| 4.1.0 | 9 / 16 | |
| 4.0.0 | 9 / 16 | |
| 3.8.3 | 10 / 13 | |
| 3.8.2 | 10 / 13 | |
| 3.8.1 | 10 / 13 | |
| 3.8.0 | 10 / 13 | |
| 3.7.0 | 10 / 13 |
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.