← Home

@okxweb3/coin-solana

3
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

xiao.xumoxixiimartynyantoringonalinus.wangdebuggorjjay98shisilunpm-okx

Keywords

solanawalletweb3cryptoblockchainsdktransactionsigningaddressprivate-key

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@okxweb3/coin-base AI (phantom-deps): Same-org dependency; likely re-exported rather than directly imported in source. ai
phantom-deps phantom-dep:@okxweb3/crypto-lib AI (phantom-deps): Same-org dependency; stable false positive for this package. ai
phantom-deps phantom-dep:borsh AI (phantom-deps): Referenced in config files; known Solana ecosystem dep, stable false positive. ai
phantom-deps phantom-dep:@noble/curves AI (phantom-deps): Referenced in config files; well-known crypto dep, stable false positive. ai
phantom-deps phantom-dep:@metaplex-foundation/beet AI (phantom-deps): Referenced in config files; known Metaplex dep, stable false positive. ai
provenance no-provenance AI (provenance): OKX wallet SDK monorepo; no provenance is consistent across all versions of this package family. ai

Versions (showing 3 of 3)

Version Deps Published
2.4.12 5 / 0
2.4.8 5 / 0
2.4.2 5 / 0

v2.4.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.8

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.

v2.4.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.