← Home

@psf/bitcoincashjs-lib

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

psf-accountchris.troutner

Keywords

bitcoinjsbitcoinbrowserifyjavascriptbitcoinjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is core to Bitcoin library functionality (parsing transactions/blocks); pattern is identical to upstream bitcoinjs-lib. ai
dependencies unvetted-dep:merkle-lib AI (dependencies): merkle-lib is a well-known Bitcoin utility package; standard dependency for this type of library. ai
dependencies unvetted-dep:@psf/bitcoincash-ops AI (dependencies): PSF-namespaced fork of bitcoincash-ops; expected dependency for this Bitcoin Cash library. ai
dependencies unvetted-dep:@psf/pushdata-bitcoin AI (dependencies): PSF-namespaced fork of pushdata-bitcoin; expected dependency for this Bitcoin Cash library. ai

Versions (showing 1 of 1)

Version Deps Published
4.0.3 15 / 12

v4.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.