@request/promise-core
Core Promise support implementation for the simplified HTTP request client 'request'.
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): This is a legitimate namespace placeholder by the established `request` publisher; 0.0.0 reflects a stub/reservation, not malicious intent. | ai | |
| provenance | publisher-changed | AI (provenance): The transition from 'request' to 'analog-nico' is the documented legitimate maintainer handoff; analog-nico is the named author in package.json and has a clean track record. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Early stub release (v0.0.1) of a known ecosystem package; tiny payload and minimal README are expected at this stage. | ai |
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
2 findingsThis version was published by a different npm account than previous versions on 2016-05-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.