@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:make-concurrent | AI (phantom-deps): Used indirectly via config; consistent with established Exodus monorepo patterns. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-wide maintainer list cleanup, not an isolated takeover signal. | ai | |
| provenance | publisher-changed | AI (provenance): CI-based publish (GitHub Actions) for established Exodus monorepo package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): bs58 is a standard, widely-used encoding lib appropriate for Solana address handling. | ai | |
| dependencies | unvetted-dep:@exodus/simple-retry | AI (dependencies): First-party @exodus org dependency; stable pattern across all versions. | 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:minimalistic-assert | AI (dependencies): Well-known utility library; no malicious history. | 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 | |
| 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 | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex-decoding a private key for auth keypair is expected crypto usage in a Solana wallet library. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 3.36.2 | 21 / 3 | |
| 3.34.1 | 20 / 3 | |
| 3.31.1 | 20 / 3 | |
| 3.30.8 | 20 / 3 | |
| 3.27.7 | 20 / 3 | |
| 3.27.3 | 20 / 3 | |
| 3.27.2 | 20 / 3 | |
| 3.25.0 | 20 / 3 | |
| 3.22.0 | 20 / 3 | |
| 3.20.2 | 18 / 3 | |
| 3.20.1 | 18 / 3 | |
| 3.20.0 | 18 / 3 | |
| 3.17.4 | 19 / 3 | |
| 3.17.3 | 19 / 3 | |
| 3.17.2 | 19 / 3 | |
| 3.17.1 | 19 / 3 | |
| 3.17.0 | 19 / 3 | |
| 3.16.0 | 19 / 2 | |
| 3.15.1 | 19 / 2 | |
| 3.15.0 | 19 / 2 | |
| 3.14.7 | 19 / 2 | |
| 3.14.6 | 19 / 2 | |
| 3.14.5 | 19 / 2 | |
| 3.14.4 | 19 / 2 | |
| 3.14.3 | 19 / 2 | |
| 3.14.2 | 19 / 2 | |
| 3.14.1 | 19 / 2 | |
| 3.14.0 | 19 / 2 | |
| 3.13.7 | 19 / 2 | |
| 3.13.6 | 20 / 2 | |
| 3.13.5 | 20 / 2 | |
| 3.13.4 | 20 / 2 | |
| 3.13.3 | 20 / 2 | |
| 3.13.2 | 20 / 2 | |
| 3.13.1 | 20 / 2 | |
| 3.13.0 | 20 / 2 | |
| 3.12.1 | 20 / 2 | |
| 3.12.0 | 20 / 2 | |
| 3.11.9 | 20 / 2 | |
| 3.11.8 | 20 / 2 | |
| 3.11.7 | 20 / 2 | |
| 3.11.6 | 20 / 2 | |
| 3.11.5 | 20 / 2 | |
| 3.11.4 | 20 / 2 | |
| 3.11.3 | 20 / 2 | |
| 3.11.2 | 20 / 2 | |
| 3.11.1 | 20 / 2 | |
| 3.11.0 | 20 / 2 |
v3.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.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.11.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.