@backstage-community/plugin-ocm-common
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 3.23.0 | 0 / 2 | |
| 3.22.0 | 0 / 2 | |
| 3.21.0 | 0 / 2 | |
| 3.20.0 | 0 / 2 | |
| 3.19.1 | 0 / 2 | |
| 3.19.0 | 0 / 2 | |
| 3.18.0 | 0 / 2 | |
| 3.17.0 | 0 / 2 | |
| 3.16.0 | 0 / 2 | |
| 3.15.0 | 0 / 2 | |
| 3.14.0 | 0 / 2 | |
| 3.13.0 | 0 / 2 | |
| 3.12.0 | 0 / 2 | |
| 3.11.0 | 0 / 2 | |
| 3.10.0 | 0 / 2 | |
| 3.9.1 | 0 / 2 | |
| 3.9.0 | 0 / 2 | |
| 3.8.3 | 0 / 2 | |
| 3.8.2 | 0 / 3 | |
| 3.8.1 | 0 / 3 | |
| 3.8.0 | 0 / 4 | |
| 3.7.0 | 0 / 4 | |
| 3.6.3 | 0 / 4 | |
| 3.6.2 | 0 / 4 | |
| 3.6.1 | 0 / 4 |
v3.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.