@privateaim/storage-kit
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@validup/zod | AI (dependencies): Direct replacement for @validup/adapter-zod within the same validup ecosystem; low risk for this package. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.11.5 | 3 / 4 | |
| 0.11.4 | 3 / 4 | |
| 0.11.3 | 3 / 4 | |
| 0.11.2 | 3 / 4 | |
| 0.11.1 | 3 / 4 | |
| 0.11.0 | 3 / 4 | |
| 0.10.3 | 3 / 4 | |
| 0.10.2 | 3 / 4 | |
| 0.10.1 | 3 / 4 | |
| 0.10.0 | 3 / 4 | |
| 0.8.45 | 3 / 4 | |
| 0.8.43 | 3 / 4 | |
| 0.8.42 | 3 / 4 | |
| 0.8.41 | 3 / 4 | |
| 0.8.39 | 0 / 4 | |
| 0.8.38 | 0 / 4 | |
| 0.8.37 | 0 / 4 | |
| 0.8.36 | 0 / 4 | |
| 0.8.34 | 0 / 4 | |
| 0.8.33 | 0 / 4 | |
| 0.8.32 | 0 / 4 | |
| 0.8.31 | 0 / 4 | |
| 0.8.30 | 0 / 4 | |
| 0.8.29 | 0 / 4 | |
| 0.8.28 | 0 / 4 | |
| 0.8.27 | 0 / 4 | |
| 0.8.26 | 0 / 4 | |
| 0.8.25 | 0 / 4 | |
| 0.8.23 | 0 / 4 | |
| 0.8.22 | 0 / 4 | |
| 0.8.21 | 0 / 4 | |
| 0.8.20 | 0 / 4 | |
| 0.8.19 | 0 / 4 | |
| 0.8.18 | 0 / 4 | |
| 0.8.17 | 0 / 4 | |
| 0.8.16 | 0 / 4 | |
| 0.8.15 | 0 / 4 | |
| 0.8.14 | 0 / 4 | |
| 0.8.13 | 0 / 4 | |
| 0.8.12 | 0 / 4 | |
| 0.8.11 | 0 / 4 | |
| 0.8.10 | 0 / 4 | |
| 0.8.9 | 0 / 4 | |
| 0.8.8 | 0 / 4 | |
| 0.8.7 | 0 / 4 | |
| 0.8.6 | 0 / 4 | |
| 0.8.5 | 0 / 4 | |
| 0.8.4 | 0 / 4 | |
| 0.8.3 | 0 / 4 | |
| 0.8.2 | 0 / 4 | |
| 0.8.1 | 0 / 4 | |
| 0.8.0 | 0 / 4 | |
| 0.7.0 | 0 / 4 | |
| 0.6.0 | 0 / 4 | |
| 0.5.0 | 0 / 4 | |
| 0.4.0 | 0 / 4 |
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.