@backstage-community/plugin-adr
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): @types/react is declared as a dependency range matching peer React versions; standard pattern for Backstage frontend plugins. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 16 / 10 | |
| 0.25.0 | 16 / 10 | |
| 0.24.0 | 16 / 10 | |
| 0.23.0 | 16 / 10 | |
| 0.22.0 | 16 / 10 | |
| 0.21.1 | 16 / 10 | |
| 0.21.0 | 16 / 10 | |
| 0.20.0 | 16 / 10 | |
| 0.19.0 | 16 / 10 | |
| 0.18.1 | 16 / 10 | |
| 0.18.0 | 16 / 9 | |
| 0.17.2 | 16 / 9 | |
| 0.17.1 | 16 / 9 | |
| 0.17.0 | 16 / 9 | |
| 0.16.0 | 16 / 9 | |
| 0.15.0 | 16 / 9 | |
| 0.14.0 | 16 / 9 | |
| 0.13.0 | 16 / 9 | |
| 0.12.0 | 16 / 9 | |
| 0.11.0 | 16 / 9 | |
| 0.10.0 | 16 / 9 | |
| 0.9.2 | 16 / 9 | |
| 0.9.1 | 16 / 10 | |
| 0.9.0 | 16 / 10 | |
| 0.8.0 | 16 / 10 | |
| 0.7.0 | 16 / 10 | |
| 0.6.28 | 16 / 10 | |
| 0.6.27 | 16 / 10 | |
| 0.6.26 | 16 / 10 | |
| 0.6.25 | 16 / 10 | |
| 0.6.24 | 15 / 10 | |
| 0.6.23 | 15 / 10 | |
| 0.6.22 | 15 / 10 | |
| 0.6.21 | 15 / 10 | |
| 0.6.20 | 15 / 10 | |
| 0.6.19 | 14 / 10 |
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.