@exodus/solana-lib
Solana utils, such as for cryptography, address encoding/decoding, transaction building, etc.
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used for Solana address encoding (bs58.encode from hex pubkey); legitimate cryptographic operation in this library. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding used to deserialize Solana wire transactions; standard operation for this library. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.24.1 | 13 / 4 | |
| 3.23.0 | 13 / 4 | |
| 3.22.6 | 12 / 4 | |
| 3.22.5 | 12 / 4 | |
| 3.22.4 | 12 / 4 |
v3.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.