unstorage
Universal Storage Layer
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in azure-key-vault driver is standard Azure Key Vault integration code for decoding secret values; not a malicious payload. | ai | |
| dependencies | unvetted-dep:h3 | AI (dependencies): h3 is a well-known unjs HTTP framework maintained by the same author (pi0); legitimate ecosystem dependency. | ai | |
| dependencies | unvetted-dep:destr | AI (dependencies): destr is a well-known unjs safe JSON deserializer maintained by the same author (pi0); legitimate ecosystem dependency. | ai | |
| dependencies | unvetted-dep:ofetch | AI (dependencies): ofetch is a well-known unjs fetch wrapper maintained by the same author (pi0); legitimate ecosystem dependency. | ai | |
| dependencies | unvetted-dep:node-fetch-native | AI (dependencies): node-fetch-native is a well-known unjs package maintained by the same author (pi0); legitimate ecosystem dependency. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.17.5 | 8 / 51 | |
| 1.17.4 | 8 / 51 | |
| 1.17.3 | 8 / 51 | |
| 1.17.2 | 8 / 51 | |
| 1.17.1 | 8 / 51 | |
| 1.17.0 | 8 / 51 | |
| 1.16.1 | 8 / 50 |
v1.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.