← Home

request-promise

The simplified HTTP request client 'request' with Promise support. Powered by Bluebird.

42
Versions
ISC
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

analog-nicomikealnylenrequestsimovtyabonil

Keywords

xhrhttphttpspromiserequestthenthenablebluebird

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:request AI (dependencies): request is the core dependency this package wraps by design; flagging it as unvetted is a stable false positive for request-promise. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by years; absence of attestation is expected and not a risk signal for this established package. ai

Versions (showing 42 of 42)

Version Deps Published
4.2.6 4 / 13
4.2.5 4 / 13
4.2.4 4 / 13
4.2.3 4 / 13
4.2.2 4 / 13
4.2.1 4 / 13
4.2.0 3 / 13
4.1.1 3 / 13
4.1.0 3 / 13
4.0.2 3 / 13
4.0.1 3 / 13
4.0.0 3 / 13
3.0.0 3 / 17
2.0.1 3 / 17
2.0.0 3 / 17
1.0.2 4 / 15
1.0.1 4 / 15
1.0.0 4 / 15
0.4.3 4 / 11
0.4.2 4 / 11
0.4.1 4 / 11
0.4.0 4 / 10
0.3.3 4 / 10
0.3.2 4 / 9
0.3.1 3 / 10
0.3.0 3 / 10
0.2.7 3 / 10
0.2.6 3 / 10
0.2.5 3 / 8
0.2.4 3 / 8
0.2.2 2 / 2
0.2.1 2 / 2
0.2.0 2 / 2
0.1.4 2 / 2
0.1.3 2 / 2
0.1.2 2 / 2
0.1.1 2 / 2
0.1.0 2 / 2
0.0.4 2 / 2
0.0.3 2 / 2
0.0.2 2 / 0
0.0.1 1 / 0

v4.2.6

1 finding
LOW No provenance attestation provenance

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

v4.2.5

1 finding
LOW No provenance attestation provenance

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

v4.2.4

1 finding
LOW No provenance attestation provenance

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

v4.2.3

1 finding
LOW No provenance attestation provenance

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

v4.2.2

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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