← Home

@bitpay-labs/bitcore-p2p-cash

npm Repository Homepage
9
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

nitsujlangstonkajoseph2

Keywords

bitcoinbitcore

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:hex-decode AI (semgrep): Hex decoding used for Bitcoin hash handling (buffer reversal); standard cryptographic pattern in this library. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads P2P command modules by name from a fixed local directory; not arbitrary user input. ai
npm-metadata url-dep:buffers AI (npm-metadata): BitPay fork of node-buffers pinned to a specific tag; consistent with this monorepo's dependency pattern. ai
phantom-deps phantom-dep:@bitpay-labs/bitcore-lib AI (phantom-deps): Same-org dependency; likely used transitively or in build tooling rather than direct import. ai

Versions (showing 9 of 9)

Version Deps Published
11.9.0 5 / 5
11.8.1 5 / 5
11.7.3 5 / 5
11.7.2 5 / 5
11.7.0 5 / 5
11.6.6 5 / 5
11.6.4 5 / 5
11.6.0 5 / 5
11.5.1 5 / 5

v11.9.0

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.

v11.8.1

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.

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

v11.7.2

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.

v11.7.0

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.

v11.6.6

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.

v11.6.4

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.

v11.6.0

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.

v11.5.1

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.