@usebruno/requests
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/qs | AI (phantom-deps): @types packages are framework-loaded by convention; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped utility package; missing metadata is common and not indicative of malice here. | ai | |
| typosquat | typosquat.levenshtein:request | AI (typosquat): Scoped @usebruno org package; not a typosquat of 'request', stable across all versions. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Fires only in test spec file saving/restoring process.env; not production code. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs are localhost (127.0.0.1:8200) in unit test assertions for Vault client; not production network calls. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 17 / 16 | |
| 0.7.0 | 2 / 13 | |
| 0.6.0 | 2 / 13 | |
| 0.5.0 | 2 / 8 | |
| 0.4.0 | 2 / 8 | |
| 0.3.0 | 1 / 8 | |
| 0.2.0 | 1 / 8 |
v0.17.0
3 findingsPackage name '@usebruno/requests' is 1 edit(s) away from popular package 'request'.
Spreading entire process.env into an object — may capture all secrets 16 | jest.useFakeTimers(); 17 | detector = new SystemProxyResolver(); > 18 | originalEnv = { ...process.env }; 19 | 20 | // Clear environment variables
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.