@bitpay-labs/bitcore-lib-ltc
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Crypto library; hex encode/decode of addresses and hashes is core functionality, not obfuscation. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is the standard ECC library used across the Bitcoin/Litecoin JS ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present to elevate this. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 11.8.1 | 8 / 5 | |
| 11.7.0 | 8 / 5 | |
| 11.6.4 | 8 / 5 | |
| 11.6.0 | 8 / 5 |
v11.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.