@backstage-community/plugin-vault-backend
A Backstage backend plugin that integrates towards Vault
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage-community/plugin-vault-node | AI (dependencies): Sibling package in the same Backstage community vault plugin family; expected dependency. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Declared runtime dep in package.json for Backstage backend plugin; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:helmet | AI (phantom-deps): Declared runtime dep in package.json for Backstage backend plugin; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Declared runtime dep in package.json for Backstage backend plugin; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:compression | AI (phantom-deps): Declared runtime dep in package.json for Backstage backend plugin; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Framework-scoped type package; expected in Backstage backend plugin context. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Declared runtime dep in package.json for Backstage backend plugin; phantom-dep heuristic false positive. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.23.0 | 15 / 11 | |
| 0.22.1 | 15 / 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.0 | 15 / 11 | |
| 0.15.0 | 15 / 11 | |
| 0.14.0 | 15 / 11 | |
| 0.13.0 | 15 / 11 | |
| 0.12.0 | 15 / 11 | |
| 0.11.0 | 15 / 11 | |
| 0.10.0 | 15 / 11 |
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.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 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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.