libsodium-wrappers-sumo
The Sodium cryptographic library compiled to pure JavaScript (wrappers, sumo variant)
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:libsodium-sumo | AI (dependencies): libsodium-sumo is the canonical companion package in the same libsodium.js project; this dependency relationship is expected and stable across all versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.8.4 | 1 / 1 | |
| 0.8.3 | 1 / 1 | |
| 0.8.2 | 1 / 1 | |
| 0.8.1 | 1 / 1 | |
| 0.8.0 | 1 / 1 | |
| 0.7.16 | 1 / 1 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.