@backstage-community/plugin-tech-radar-common
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.19.0 | 1 / 1 | |
| 1.18.0 | 1 / 1 | |
| 1.17.0 | 1 / 1 | |
| 1.16.0 | 1 / 1 | |
| 1.15.0 | 1 / 1 | |
| 1.14.0 | 1 / 1 | |
| 1.13.0 | 1 / 1 | |
| 1.12.0 | 1 / 1 | |
| 1.11.0 | 1 / 1 | |
| 1.10.0 | 1 / 1 | |
| 1.9.1 | 1 / 1 | |
| 1.9.0 | 1 / 1 | |
| 1.8.0 | 1 / 1 | |
| 1.7.0 | 1 / 1 | |
| 1.6.0 | 1 / 1 | |
| 1.5.0 | 1 / 1 | |
| 1.4.0 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.0 | 1 / 1 |
v1.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.