@okxweb3/coin-ethereum
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:superstruct | AI (phantom-deps): Same-org SDK; deps used transitively or in bundled dist, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@okxweb3/coin-base | AI (phantom-deps): Same org scope; used transitively in the SDK bundle. | ai | |
| phantom-deps | phantom-dep:@okxweb3/crypto-lib | AI (phantom-deps): Same org scope; used transitively in the SDK bundle. | ai | |
| phantom-deps | phantom-dep:ethereum-cryptography | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/eth-sig-util | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): OKX wallet SDK monorepo; provenance not used across the package family, stable pattern. | ai |
v2.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.