@backstage-community/plugin-azure-devops-backend
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/express | AI (phantom-deps): Backstage backend plugins conventionally declare @types/express as a runtime dep; not a real phantom. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Standard Backstage plugin pattern; referenced in config files as documented. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-node | AI (phantom-deps): Standard Backstage backend plugin dependency pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-node | AI (phantom-deps): Standard Backstage backend plugin dependency pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-common | AI (phantom-deps): Standard Backstage backend plugin dependency pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-permission-node | AI (phantom-deps): Standard Backstage backend plugin dependency pattern. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.30.1 | 18 / 5 | |
| 0.30.0 | 18 / 5 | |
| 0.29.0 | 18 / 5 | |
| 0.28.0 | 18 / 5 | |
| 0.27.0 | 18 / 5 | |
| 0.26.1 | 18 / 6 | |
| 0.26.0 | 18 / 6 | |
| 0.25.0 | 18 / 6 | |
| 0.24.1 | 18 / 6 | |
| 0.24.0 | 18 / 6 | |
| 0.23.0 | 18 / 6 | |
| 0.22.0 | 18 / 6 | |
| 0.21.0 | 18 / 6 | |
| 0.20.0 | 18 / 6 | |
| 0.19.0 | 18 / 6 | |
| 0.18.0 | 18 / 6 | |
| 0.17.1 | 18 / 6 | |
| 0.17.0 | 18 / 6 | |
| 0.16.0 | 18 / 6 | |
| 0.15.0 | 18 / 6 | |
| 0.14.0 | 18 / 6 | |
| 0.13.0 | 18 / 6 | |
| 0.12.0 | 18 / 6 | |
| 0.11.0 | 18 / 6 | |
| 0.10.1 | 18 / 6 | |
| 0.10.0 | 20 / 6 | |
| 0.9.0 | 20 / 6 | |
| 0.8.0 | 20 / 6 | |
| 0.7.3 | 21 / 6 | |
| 0.7.2 | 21 / 6 | |
| 0.7.1 | 21 / 6 | |
| 0.7.0 | 21 / 6 | |
| 0.6.12 | 21 / 6 | |
| 0.6.11 | 21 / 6 | |
| 0.6.10 | 21 / 6 | |
| 0.6.9 | 20 / 6 | |
| 0.6.8 | 20 / 6 | |
| 0.6.6 | 20 / 6 |
v0.30.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
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.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
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.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.