bluebird-retry MIT 18 versions

bluebird-retry

npm Repository Homepage

utility for retrying a bluebird promise until it succeeds

18

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

demmer

Keywords

bluebirdpromiseretry

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:browser/bluebird-retry.umd.js	AI (source-diff): The file is a standard webpack/browserify UMD bundle. The 'network + code execution' pattern is webpack bootstrap boilerplate, not malware. Bluebird bundles legitimately include this pattern.	ai	2026/04/23
semgrep	semgrep:new-function-constructor	AI (semgrep): Occurs inside an `if (false)` dead-code block in the bluebird bundle. Never executed at runtime; this is a known bluebird optimization pattern.	ai	2026/04/23
semgrep	semgrep:eval-usage	AI (semgrep): The eval() call appears after a return statement (unreachable dead code) in the bluebird bundle. Not a real execution risk.	ai	2026/04/23
source-diff	source-size-tripled	AI (source-diff): Size increase is entirely due to addition of a browser UMD bundle, consistent with devDependencies (browserify, vinyl-source-stream) and the files field listing browser/*.js.	ai	2026/04/23

Versions (showing 18 of 18)

Version	Deps	Published
0.11.0	0 / 12	2017-06-14
0.10.1	0 / 12	2016-11-26
0.10.0	0 / 12	2016-11-26
0.9.0	0 / 12	2016-11-24
0.8.0	0 / 12	2016-07-27
0.7.0	0 / 11	2016-06-16
0.6.1	0 / 11	2016-04-17
0.6.0	0 / 11	2016-03-28
0.5.3	1 / 4	2016-01-14
0.5.2	1 / 4	2015-10-16
0.5.1	1 / 4	2015-08-27
0.5.0	2 / 3	2015-07-28
0.4.0	2 / 3	2015-04-19
0.3.2	2 / 3	2015-03-18
0.3.1	2 / 3	2015-01-10
0.3.0	2 / 3	2015-01-02
0.2.0	2 / 3	2014-11-09
0.1.0	2 / 3	2014-11-06

v0.11.0

2 findings

HIGH New file with network + code execution: browser/bluebird-retry.umd.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

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.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.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.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.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

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.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.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.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

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.