@polkadot-api/smoldot-patch
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:dist/cjs/internals/bytecode/wasm0.js | AI (source-diff): Base64-encoded WASM bytecode is the core artifact of the smoldot light client; stable pattern across versions. | ai | |
| source-diff | encoded-string-file:dist/mjs/internals/bytecode/wasm0.js | AI (source-diff): Same WASM bytecode in ESM format; expected for this package. | ai | |
| source-diff | encoded-string-file:dist/cjs/internals/bytecode/wasm1.js | AI (source-diff): WASM bytecode artifact; expected for smoldot. | ai | |
| source-diff | encoded-string-file:dist/mjs/internals/bytecode/wasm1.js | AI (source-diff): WASM bytecode artifact; expected for smoldot. | ai | |
| source-diff | encoded-string-file:dist/cjs/internals/bytecode/wasm2.js | AI (source-diff): WASM bytecode artifact; expected for smoldot. | ai | |
| source-diff | encoded-string-file:dist/mjs/internals/bytecode/wasm2.js | AI (source-diff): WASM bytecode artifact; expected for smoldot. | ai |
v103.0.0
7 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified 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.
v102.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.