@polkadot/wasm-schnorrkel
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:wasm_wasm.js | AI (source-diff): The long encoded string is the compiled WASM binary (base64-encoded) — standard packaging pattern for @polkadot/wasm-* packages. Not a malicious payload. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Standard wasm-bindgen JS glue code pattern; new Function() is used to construct functions from WASM memory strings, not to execute attacker-controlled input. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 content is the compiled WASM binary (Schnorrkel crypto) bundled inline — a standard pattern for WASM packages, not a hidden payload. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 0 / 1 | |
| 0.6.1 | 0 / 1 | |
| 0.5.1 | 0 / 1 | |
| 0.4.1 | 0 / 1 | |
| 0.3.1 | 0 / 1 | |
| 0.2.1 | 0 / 1 | |
| 0.1.1 | 0 / 1 |
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.