← Home

cls-bluebird

npm Repository Homepage

Make bluebird work with the continuation-local-storage module.

9
Versions
BSD-2-Clause
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

overlookmoteltimbeyer

Keywords

continuation-local-storageclsbluebirdcontinuationlocalstoragepromisepromisesasyncthreadgluebaling-wirepatch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change occurred in 2016; overlookmotel has 12 approved packages and a long track record. This is a settled, legitimate maintainer transition. ai
source-diff source-size-tripled AI (source-diff): Size increase from 820B to 4KB is modest in absolute terms and consistent with legitimate feature expansion of a CLS shim. No injected payloads or obfuscation detected. ai

Versions (showing 9 of 9)

Version Deps Published
2.1.0 2 / 10
2.0.1 2 / 10
2.0.0 2 / 10
1.1.3 2 / 5
1.1.2 2 / 4
1.1.1 2 / 4
1.1.0 1 / 4
1.0.1 1 / 2
1.0.0 1 / 2

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH Publisher changed: timbeyer → overlookmotel (on 2016-06-18) provenance

This version was published by a different npm account than previous versions on 2016-06-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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