@backstage-community/plugin-azure-devops
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 a peer/dev type dep in Backstage plugins; stable false positive for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.32.1 | 18 / 11 | |
| 0.32.0 | 18 / 11 | |
| 0.31.0 | 18 / 11 | |
| 0.30.0 | 18 / 11 | |
| 0.29.0 | 18 / 11 | |
| 0.28.2 | 18 / 11 | |
| 0.28.1 | 18 / 11 | |
| 0.28.0 | 18 / 11 | |
| 0.27.0 | 18 / 11 | |
| 0.26.0 | 17 / 11 | |
| 0.25.0 | 17 / 11 | |
| 0.24.1 | 17 / 11 | |
| 0.24.0 | 17 / 11 | |
| 0.23.0 | 17 / 11 | |
| 0.22.0 | 15 / 11 | |
| 0.21.0 | 15 / 11 | |
| 0.20.0 | 15 / 11 | |
| 0.19.0 | 15 / 11 | |
| 0.18.0 | 15 / 11 | |
| 0.17.0 | 15 / 11 | |
| 0.16.1 | 15 / 11 | |
| 0.16.0 | 15 / 11 | |
| 0.15.0 | 15 / 11 | |
| 0.14.0 | 15 / 11 | |
| 0.13.2 | 15 / 11 | |
| 0.13.1 | 15 / 12 | |
| 0.13.0 | 15 / 12 | |
| 0.12.0 | 15 / 12 | |
| 0.11.0 | 15 / 12 | |
| 0.10.0 | 15 / 12 | |
| 0.9.0 | 15 / 12 | |
| 0.8.0 | 15 / 12 | |
| 0.7.0 | 15 / 12 | |
| 0.6.3 | 15 / 12 | |
| 0.6.2 | 16 / 12 | |
| 0.6.1 | 15 / 12 | |
| 0.6.0 | 15 / 12 | |
| 0.5.1 | 15 / 12 | |
| 0.5.0 | 15 / 12 | |
| 0.4.10 | 15 / 12 | |
| 0.4.9 | 15 / 12 | |
| 0.4.8 | 15 / 12 | |
| 0.4.7 | 15 / 12 | |
| 0.4.5 | 15 / 12 |
v0.32.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.