@newrelic/nr-labs-components
New Relic Labs components
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 2 / 32 | |
| 2.0.5 | 2 / 31 | |
| 2.0.4 | 2 / 31 | |
| 2.0.3 | 2 / 31 | |
| 2.0.2 | 2 / 29 | |
| 2.0.1 | 2 / 29 | |
| 2.0.0 | 2 / 29 |
v2.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.