@polpo-ai/vault-crypto
AES-256-GCM encryption helpers for Polpo vault stores
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small scoped crypto helper; no provenance is a hygiene gap but not a security disqualifier for this package. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 0 / 1 | |
| 0.8.0 | 0 / 1 | |
| 0.7.18 | 0 / 1 | |
| 0.7.17 | 0 / 1 | |
| 0.7.16 | 0 / 1 | |
| 0.7.14 | 0 / 1 | |
| 0.7.13 | 0 / 1 | |
| 0.7.12 | 0 / 1 | |
| 0.7.11 | 0 / 1 | |
| 0.7.10 | 0 / 1 | |
| 0.7.9 | 0 / 1 | |
| 0.7.8 | 0 / 1 | |
| 0.7.7 | 0 / 1 | |
| 0.7.6 | 0 / 1 | |
| 0.7.5 | 0 / 1 | |
| 0.7.4 | 0 / 1 | |
| 0.7.3 | 0 / 1 | |
| 0.7.2 | 0 / 1 | |
| 0.7.1 | 0 / 1 | |
| 0.7.0 | 0 / 1 | |
| 0.6.32 | 0 / 1 | |
| 0.6.31 | 0 / 1 | |
| 0.6.30 | 0 / 1 | |
| 0.6.29 | 0 / 1 | |
| 0.6.28 | 0 / 1 | |
| 0.6.27 | 0 / 1 | |
| 0.6.26 | 0 / 1 | |
| 0.6.25 | 0 / 1 | |
| 0.6.24 | 0 / 1 | |
| 0.6.23 | 0 / 1 | |
| 0.6.22 | 0 / 1 | |
| 0.6.21 | 0 / 1 | |
| 0.6.20 | 0 / 1 | |
| 0.6.19 | 0 / 1 | |
| 0.6.18 | 0 / 1 | |
| 0.6.15 | 0 / 1 | |
| 0.6.14 | 0 / 1 | |
| 0.6.13 | 0 / 1 | |
| 0.6.12 | 0 / 1 | |
| 0.6.11 | 0 / 1 | |
| 0.6.10 | 0 / 1 | |
| 0.6.9 | 0 / 1 | |
| 0.6.7 | 0 / 1 | |
| 0.6.6 | 0 / 1 | |
| 0.6.5 | 0 / 1 | |
| 0.6.4 | 0 / 1 | |
| 0.6.3 | 0 / 1 | |
| 0.6.2 | 0 / 1 | |
| 0.6.1 | 0 / 1 | |
| 0.6.0 | 0 / 1 | |
| 0.5.25 | 0 / 1 |
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
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.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.