@scrypt-inc/bsv
1
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
zhfnjust
Keywords
bitcoinbsvscrypttransactionaddressp2peciescryptocurrencyblockchainpaymentbip21bip32bip37bip69bip70multisig
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped BSV Bitcoin library; no relation to 'qs'. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped BSV Bitcoin library; no relation to 'ajv'. Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:clone-deep | AI (phantom-deps): clone-deep is a declared runtime dependency; phantom-dep heuristic false positive. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 10 / 7 |
v1.0.5
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.