launchdarkly-js-sdk-common
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; expected for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): LaunchDarkly SDK with 2M downloads; dormancy reflects maintenance cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive on established SDK; README links are API docs, not spam. | ai | |
| phantom-deps | phantom-dep:base64-js | AI (phantom-deps): base64-js is properly declared in dependencies and used in build/bundling; phantom-dep false positive for SDK libraries. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): fast-deep-equal is properly declared in dependencies and used in build/bundling; phantom-dep false positive for SDK libraries. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.8.1 | 2 / 25 | |
| 5.8.0 | 3 / 25 | |
| 5.7.1 | 3 / 25 | |
| 5.7.0 | 3 / 25 | |
| 5.6.0 | 3 / 25 | |
| 5.5.1 | 3 / 25 | |
| 5.5.0 | 3 / 25 | |
| 5.4.0 | 3 / 25 | |
| 5.3.0 | 3 / 25 | |
| 5.2.0 | 3 / 24 | |
| 5.1.0 | 3 / 24 | |
| 5.0.3 | 3 / 23 | |
| 5.0.2 | 3 / 23 | |
| 5.0.1 | 3 / 23 | |
| 5.0.0 | 3 / 23 | |
| 4.3.3 | 3 / 22 | |
| 4.3.2 | 3 / 22 | |
| 4.3.1 | 3 / 22 | |
| 4.3.0 | 3 / 22 | |
| 4.2.0 | 3 / 22 | |
| 4.1.1 | 3 / 22 | |
| 4.1.0 | 3 / 22 | |
| 4.0.3 | 3 / 22 | |
| 4.0.2 | 3 / 22 | |
| 4.0.1 | 3 / 24 | |
| 4.0.0 | 3 / 32 |
v5.8.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.