@exodus/solana-plugin
Solana plugin for Exodus SDK powered wallets.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Exodus org regularly rotates team members; changes are within the same organization. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainers consistent with org team rotation, not a hostile takeover. | ai | |
| dependencies | unvetted-dep:minimalistic-assert | AI (dependencies): minimalistic-assert is a well-known, minimal utility with no malicious history; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@exodus/i18n-dummy | AI (dependencies): First-party Exodus stub/dummy i18n package; consistent with the org's publishing pattern. | ai | |
| provenance | no-provenance | AI (provenance): publishConfig explicitly sets provenance:false; stable policy for this publisher. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.39.0 | 11 / 1 | |
| 1.38.0 | 11 / 1 | |
| 1.37.1 | 11 / 1 | |
| 1.36.4 | 11 / 1 | |
| 1.36.3 | 11 / 1 | |
| 1.36.1 | 11 / 1 | |
| 1.33.0 | 11 / 1 | |
| 1.32.4 | 11 / 1 | |
| 1.30.5 | 11 / 1 | |
| 1.30.2 | 11 / 1 | |
| 1.29.3 | 11 / 1 | |
| 1.29.2 | 11 / 1 | |
| 1.28.1 | 11 / 1 | |
| 1.26.0 | 11 / 1 | |
| 1.24.5 | 11 / 1 | |
| 1.24.4 | 11 / 1 | |
| 1.24.2 | 11 / 1 | |
| 1.24.1 | 11 / 1 | |
| 1.23.2 | 8 / 1 | |
| 1.23.1 | 8 / 1 | |
| 1.23.0 | 8 / 1 | |
| 1.22.0 | 8 / 1 | |
| 1.21.1 | 8 / 1 | |
| 1.21.0 | 8 / 1 |
v1.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.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.
v1.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.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.
v1.28.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.
v1.26.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.
v1.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.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.
v1.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.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.
v1.23.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.
v1.22.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.
v1.21.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.
v1.21.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.