bluebird
Full featured Promises/A+ implementation with exceptionally good performance
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 |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 35 of 135)
| Version | Deps | Published |
|---|---|---|
| 2.3.6 | 0 / 25 | |
| 2.3.5 | 0 / 25 | |
| 2.3.4 | 0 / 25 | |
| 2.3.3 | 0 / 25 | |
| 2.3.2 | 0 / 25 | |
| 2.3.1 | 0 / 25 | |
| 2.3.0 | 0 / 25 | |
| 2.2.2 | 0 / 25 | |
| 2.2.1 | 0 / 25 | |
| 2.2.0 | 0 / 25 | |
| 2.1.3 | 0 / 25 | |
| 2.1.2 | 0 / 25 | |
| 2.1.1 | 0 / 25 | |
| 2.0.7 | 0 / 25 | |
| 2.0.6 | 0 / 25 | |
| 2.0.5 | 0 / 25 | |
| 2.0.4 | 0 / 25 | |
| 2.0.3 | 0 / 25 | |
| 2.0.2 | 0 / 25 | |
| 1.2.4 | 0 / 25 | |
| 1.2.3 | 0 / 25 | |
| 1.2.2 | 0 / 25 | |
| 1.2.1 | 0 / 24 | |
| 1.2.0 | 0 / 24 | |
| 1.1.1 | 0 / 24 | |
| 1.1.0 | 0 / 24 | |
| 1.0.8 | 0 / 24 | |
| 1.0.7 | 0 / 23 | |
| 1.0.5 | 0 / 23 | |
| 1.0.4 | 0 / 23 | |
| 1.0.3 | 0 / 23 | |
| 1.0.2 | 0 / 23 | |
| 1.0.1 | 0 / 23 | |
| 1.0.0 | 0 / 22 | |
| 0.11.6 | 0 / 22 |
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.