bitcore-lib
A pure and powerful JavaScript Bitcoin library.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:bitcore-lib.js | AI (source-diff): Bundled DH modp primes and crypto constants; standard for a Bitcoin/crypto library. | ai | |
| source-diff | encoded-string-file:test/block/block.js | AI (source-diff): Hex-encoded Bitcoin block data in test fixtures; expected for this package. | ai | |
| source-diff | encoded-string-file:test/transaction/input/multisig.js | AI (source-diff): Hex-encoded Bitcoin scripts/txids in test fixtures. | ai | |
| source-diff | encoded-string-file:test/transaction/input/multisigscripthash.js | AI (source-diff): Hex-encoded Bitcoin scripts in test fixtures. | ai | |
| source-diff | encoded-string-file:test/transaction/transaction.js | AI (source-diff): Test fixtures with serialized Bitcoin transactions; expected for a Bitcoin library. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding of compact signatures is standard Bitcoin message signing/verification functionality, not a malicious payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is a fundamental operation in a Bitcoin library (address hashes, transaction data). These are not obfuscated payloads — they are core cryptographic functionality. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 11.5.1 | 7 / 5 | |
| 11.4.5 | 7 / 5 | |
| 10.10.7 | 7 / 5 | |
| 10.0.36 | 8 / 5 | |
| 8.25.10 | 7 / 5 |
v11.5.1
2 findingsModified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.5
2 findingsModified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.36
6 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 33 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.25.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.