@bitpay-labs/bitcore-lib-doge
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is a standard EC cryptography dependency expected in any Bitcoin/Dogecoin library. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in a crypto library is standard for hash/key serialization; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver mirrors upstream bitcore versioning; scoped fork of a legitimate BitPay repo. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 11.8.1 | 7 / 5 | |
| 11.7.3 | 7 / 5 | |
| 11.6.6 | 7 / 5 | |
| 11.6.0 | 7 / 5 | |
| 11.5.1 | 7 / 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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.6
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.
v11.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.