@emurgo/cardano-serialization-lib-nodejs
4
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
vsubhumanstackchainlisicky_emurgotwwu123cryptotitanabdelkrimdevjarstorm
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Standard wasm-bindgen-generated JS glue code for WASM interop. The new Function() call constructs functions from WASM module strings, not external user input. Expected pattern in all wasm-bindgen Node.js targets. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard wasm-bindgen-generated __wbg_require export for Node.js module loading from WASM. Expected boilerplate in all wasm-bindgen Node.js targets for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package (2120 days, 170 versions) predating Sigstore adoption. No provenance is common and not a risk signal here. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 15.0.3 | 0 / 0 | |
| 15.0.2 | 0 / 0 | |
| 15.0.1 | 0 / 0 | |
| 15.0.0 | 0 / 0 |
v15.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.