launchdarkly-node-client-sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:launchdarkly-js-sdk-common | AI (dependencies): launchdarkly-js-sdk-common is a first-party LaunchDarkly package, a core shared library for their JS SDKs. Stable dependency for this package. | ai | |
| dependencies | unvetted-dep:launchdarkly-eventsource | AI (dependencies): launchdarkly-eventsource is a first-party LaunchDarkly package, part of the same SDK ecosystem. Stable dependency for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 3 / 18 | |
| 3.3.1 | 3 / 18 | |
| 3.3.0 | 3 / 18 | |
| 3.2.1 | 3 / 18 | |
| 3.2.0 | 3 / 18 | |
| 3.1.0 | 3 / 18 | |
| 3.0.2 | 3 / 18 | |
| 3.0.1 | 3 / 18 | |
| 3.0.0 | 3 / 18 | |
| 2.2.2 | 3 / 17 | |
| 2.2.1 | 3 / 17 | |
| 2.2.0 | 3 / 17 | |
| 2.1.0 | 3 / 17 | |
| 2.0.4 | 3 / 21 | |
| 2.0.3 | 3 / 21 | |
| 2.0.2 | 4 / 21 | |
| 2.0.1 | 4 / 21 | |
| 2.0.0 | 4 / 21 |
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.