@exodus/solana-api
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:minimalistic-assert | AI (dependencies): Well-known utility library; no malicious history. | ai | |
| dependencies | unvetted-dep:@exodus/crypto | AI (dependencies): First-party @exodus org dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@exodus/solana-lib | AI (dependencies): First-party @exodus org dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@exodus/simple-retry | AI (dependencies): First-party @exodus org dependency; stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): publishConfig explicitly sets provenance:false; stable org policy across all Exodus packages. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding Metaplex on-chain metadata from base64 is standard Solana blockchain operation, not obfuscation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex-decoding a private key for auth keypair is expected crypto usage in a Solana wallet library. | ai | |
| phantom-deps | phantom-dep:@exodus/timer | AI (phantom-deps): @exodus/timer is declared in dependencies and used indirectly; same-org scope, stable false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.34.1 | 20 / 3 | |
| 3.31.1 | 20 / 3 | |
| 3.30.8 | 20 / 3 | |
| 3.27.7 | 20 / 3 | |
| 3.20.2 | 18 / 3 | |
| 3.20.1 | 18 / 3 | |
| 3.20.0 | 18 / 3 |
v3.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.