qtum-ethers-wrapper
2
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
ripplyrjqtum
Keywords
EthereumethersQTUM
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard for Bitcoin/Ethereum transaction serialization in this library; no malicious payload pattern. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Buffer polyfill declared for bundler compatibility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:crypto | AI (phantom-deps): Node crypto polyfill declared for bundler compatibility; stable false positive. | ai | |
| phantom-deps | phantom-dep:elliptic | AI (phantom-deps): Crypto library used transitively; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:typeforce | AI (phantom-deps): Used transitively by bitcoinjs-lib ecosystem; stable false positive. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript listed as runtime dep but used as build tool; stable false positive. | ai | |
| phantom-deps | phantom-dep:safe-buffer | AI (phantom-deps): Buffer compatibility shim; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:buffer-reverse | AI (phantom-deps): Bitcoin transaction utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pushdata-bitcoin | AI (phantom-deps): Bitcoin script utility; stable false positive for this package. | ai |
v2.1.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.
v1.1.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.