scryptlib
1
Versions
—
License
Yes
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
xhliufreedomherozhfnjustmsinkecaaron67
Keywords
bsvsCryptJavascriptAPI
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall fetches prebuilt sCrypt compiler binary; consistent with documented SDK behavior across all versions. | ai | |
| dependencies | unvetted-dep:@scrypt-inc/bsv | AI (dependencies): First-party dep from the same org (@scrypt-inc); stable pattern across all scryptlib versions. | ai | |
| dependencies | unvetted-dep:get-proxy-settings | AI (dependencies): Used to support proxy-aware binary download in postinstall; benign utility dep. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.2.6 | 13 / 13 |
v2.2.6
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: node ./postinstall.js
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.