sodium-native
Low level bindings for libsodium
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): sodium-native is a native libsodium binding that legitimately ships prebuilt platform binaries; this is its documented and expected install pattern. | ai | |
| phantom-deps | phantom-dep:bare-assert | AI (phantom-deps): bare-assert is used via package.json import map conditional exports for the Bare runtime, not a direct require(); this is a legitimate pattern, not a true phantom dependency. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 3 / 7 | |
| 5.0.10 | 2 / 7 | |
| 5.0.9 | 2 / 6 | |
| 5.0.8 | 2 / 6 | |
| 5.0.7 | 2 / 6 | |
| 5.0.6 | 2 / 6 | |
| 5.0.5 | 2 / 6 | |
| 5.0.4 | 2 / 6 | |
| 5.0.3 | 2 / 6 | |
| 5.0.2 | 2 / 6 |
v5.1.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/sodium-native.bare • prebuilds/android-arm64/sodium-native.bare • prebuilds/android-ia32/sodium-native.bare • prebuilds/android-x64/sodium-native.bare • prebuilds/darwin-arm64/sodium-native.bare • prebuilds/darwin-x64/sodium-native.bare • prebuilds/ios-arm64-simulator/sodium-native.bare • prebuilds/ios-arm64/sodium-native.bare • prebuilds/ios-x64-simulator/sodium-native.bare • prebuilds/linux-arm64/sodium-native.bare ... and 13 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.