bluebird — Greenflagged

Full featured Promises/A+ implementation with exceptionally good performance

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

esailija

Keywords

promiseperformancepromisespromises-apromises-aplusasyncawaitdeferreddeferredsfutureflow controldslfluent interface

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): child_process usage is in changelog.js, a dev-only build utility not included in the published package files. No runtime risk.	ai	2026/04/24
source-diff	net-exec-file:js/main/promisify.js	AI (source-diff): Bluebird's promisify.js uses new Function() for perf-optimized wrapper generation — no actual network calls. False positive on a core, well-known library feature.	ai	2026/04/24
source-diff	net-exec-file:js/browser/bluebird.core.js	AI (source-diff): Browser bundle generated by bluebird's build tooling; UMD wrapper + new Function() for perf-optimized promise joins. Not malicious.	ai	2026/04/24
source-diff	large-new-source-files	AI (source-diff): Major version (v3) restructured build output into js/release/ and js/browser/ dirs; large file count increase is expected.	ai	2026/04/24
source-diff	net-exec-file:js/release/promisify.js	AI (source-diff): Bluebird's promisify uses new Function() for perf-optimized callback wrapping. No actual network calls present; false positive from dynamic code generation pattern.	ai	2026/04/24
semgrep	semgrep:new-function-constructor	AI (semgrep): Bluebird uses new Function() as a documented performance optimization for internal fast-path code generation; inputs are entirely internally controlled, not user-supplied.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Bluebird 3.x is a legacy package predating Sigstore provenance; absence of attestation is expected and not a risk signal for this well-established package.	ai	2026/04/23
semgrep	semgrep:eval-usage	AI (semgrep): The eval() call in Bluebird appears after a return statement (dead code) and is a known V8 de-optimization trick; it is never actually executed.	ai	2026/04/23

Versions (showing 51 of 135)

View all versions

Version	Deps	Published
3.7.2	0 / 25	2019-11-28
3.7.1	0 / 25	2019-10-15
3.7.0	0 / 25	2019-10-01
3.6.0	0 / 25	2019-10-01
3.5.5	0 / 25	2019-05-24
3.5.4	0 / 25	2019-04-03
3.5.3	0 / 25	2018-11-06
3.5.2	0 / 24	2018-09-03
3.5.1	0 / 24	2017-10-04
3.5.0	0 / 24	2017-03-03
3.4.7	0 / 24	2016-12-22
3.4.6	0 / 24	2016-09-01
3.4.5	0 / 24	2016-08-31
3.4.4	0 / 24	2016-08-30
3.4.3	0 / 24	2016-08-25
3.4.2	0 / 24	2016-08-24
3.4.1	0 / 24	2016-06-17
3.4.0	0 / 24	2016-05-17
3.3.5	0 / 24	2016-04-12
3.3.4	0 / 24	2016-03-07
3.3.3	0 / 24	2016-02-25
3.3.2	0 / 24	2016-02-25
3.3.1	0 / 24	2016-02-13
3.3.0	0 / 24	2016-02-12
3.2.2	0 / 24	2016-02-05
3.2.1	0 / 24	2016-02-01
3.2.0	0 / 25	2016-02-01
3.1.5	0 / 24	2016-01-26
3.1.4	0 / 24	2016-01-25
3.1.3	0 / 24	2016-01-25
3.1.2	0 / 24	2016-01-23
3.1.1	0 / 24	2015-12-16
3.1.0	0 / 24	2015-12-16
3.0.6	0 / 24	2015-12-01
3.0.5	0 / 24	2015-11-01
3.0.4	0 / 24	2015-11-01
3.0.3	0 / 24	2015-11-01
3.0.2	0 / 24	2015-10-29
3.0.1	0 / 24	2015-10-28
3.0.0	0 / 24	2015-10-27
2.11.0	0 / 24	2016-08-30
2.10.2	0 / 24	2015-10-01
2.10.1	0 / 24	2015-09-21
2.10.0	0 / 24	2015-09-08
2.9.34	0 / 24	2015-07-15
2.9.33	0 / 24	2015-07-09
2.9.32	0 / 24	2015-07-03
2.9.31	0 / 24	2015-07-03
2.9.30	0 / 24	2015-06-14
2.9.29	0 / 24	2015-06-14
2.9.28	0 / 24	2015-06-14

v3.7.1

1 finding

INFO No provenance attestation provenance

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

v3.7.0

1 finding

INFO No provenance attestation provenance

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

v3.6.0

1 finding

INFO No provenance attestation provenance

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

v3.5.5

1 finding

INFO No provenance attestation provenance

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

v3.5.4

1 finding

INFO No provenance attestation provenance

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

v3.5.3

1 finding

INFO No provenance attestation provenance

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

v3.5.2

1 finding

INFO No provenance attestation provenance

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

v3.5.1

1 finding

INFO No provenance attestation provenance

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

v3.5.0

1 finding

INFO No provenance attestation provenance

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

v3.4.7

1 finding

LOW No provenance attestation provenance

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

v3.4.6

1 finding

INFO No provenance attestation provenance

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

v3.4.5

1 finding

INFO No provenance attestation provenance

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

v3.4.4

1 finding

INFO No provenance attestation provenance

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

v3.4.3

1 finding

INFO No provenance attestation provenance

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

v3.4.2

1 finding

INFO No provenance attestation provenance

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

v3.4.1

1 finding

INFO No provenance attestation provenance

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

v3.4.0

1 finding

INFO No provenance attestation provenance

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

v3.3.5

1 finding

INFO No provenance attestation provenance

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

v3.3.4

1 finding

INFO No provenance attestation provenance

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

v3.3.3

1 finding

INFO No provenance attestation provenance

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

v3.3.2

1 finding

INFO No provenance attestation provenance

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

v3.3.1

1 finding

INFO No provenance attestation provenance

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

v3.3.0

1 finding

INFO No provenance attestation provenance

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

v3.2.2

1 finding

INFO No provenance attestation provenance

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

v3.2.1

1 finding

INFO No provenance attestation provenance

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

v3.2.0

1 finding

INFO No provenance attestation provenance

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

v3.1.5

1 finding

INFO No provenance attestation provenance

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

v3.1.4

2 findings

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

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

INFO No provenance attestation provenance

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

v3.1.3

1 finding

INFO No provenance attestation provenance

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

v3.1.2

1 finding

INFO No provenance attestation provenance

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

v3.1.1

1 finding

INFO No provenance attestation provenance

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

v3.1.0

1 finding

INFO No provenance attestation provenance

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

v3.0.6

1 finding

INFO No provenance attestation provenance

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

v3.0.5

1 finding

INFO No provenance attestation provenance

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

v3.0.4

1 finding

INFO No provenance attestation provenance

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

v3.0.3

1 finding

INFO No provenance attestation provenance

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

v3.0.2

1 finding

INFO No provenance attestation provenance

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

v3.0.1

1 finding

INFO No provenance attestation provenance

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

v3.0.0

2 findings

HIGH New file with network + code execution: js/release/promisify.js source-diff

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

INFO No provenance attestation provenance

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

v2.11.0

2 findings

HIGH New file with network + code execution: js/main/promisify.js source-diff

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

INFO No provenance attestation provenance

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

v2.10.2

1 finding

INFO No provenance attestation provenance

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

v2.10.1

1 finding

INFO No provenance attestation provenance

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

v2.10.0

1 finding

INFO No provenance attestation provenance

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

v2.9.34

1 finding

INFO No provenance attestation provenance

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

v2.9.33

1 finding

INFO No provenance attestation provenance

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

v2.9.32

1 finding

INFO No provenance attestation provenance

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

v2.9.31

1 finding

INFO No provenance attestation provenance

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

v2.9.30

1 finding

INFO No provenance attestation provenance

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

v2.9.29

1 finding

INFO No provenance attestation provenance

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

v2.9.28

1 finding

INFO No provenance attestation provenance

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