@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 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.25.0 | 15 / 11 | |
| 0.24.0 | 15 / 11 | |
| 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 | |
| 0.9.0 | 15 / 11 | |
| 0.8.1 | 15 / 11 | |
| 0.8.0 | 15 / 10 | |
| 0.7.0 | 15 / 10 | |
| 0.6.0 | 15 / 10 | |
| 0.5.2 | 15 / 10 | |
| 0.5.1 | 15 / 10 | |
| 0.5.0 | 16 / 10 | |
| 0.4.21 | 16 / 10 | |
| 0.4.20 | 17 / 10 | |
| 0.4.19 | 17 / 10 | |
| 0.4.18 | 17 / 7 | |
| 0.4.17 | 17 / 7 | |
| 0.4.16 | 17 / 7 | |
| 0.4.15 | 16 / 7 | |
| 0.4.14 | 16 / 7 | |
| 0.4.12 | 16 / 7 | |
| 0.4.11 | 16 / 7 |
v0.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
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.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.