@varlock/hashicorp-vault-plugin
Varlock plugin to load secrets from HashiCorp Vault (KV v2 secrets engine) / OpenBao
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a placeholder reservation in a known monorepo; not indicative of malicious intent for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Empty payload is expected for a stub/placeholder package in a monorepo pre-release slot. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 6 | |
| 0.0.4 | 0 / 6 | |
| 0.0.3 | 0 / 6 | |
| 0.0.2 | 0 / 6 | |
| 0.0.0 | 0 / 0 |
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.