@exodus/ethereum-plugin
Ethereum 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Exodus org migrated to GitHub Actions publishing; consistent with their CI/CD workflow across packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Exodus org team rotation; consistent with internal maintainer management across their package portfolio. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added; org-level rotation, not a hostile takeover signal. | ai | |
| dependencies | unvetted-dep:@exodus/simple-retry | AI (dependencies): First-party @exodus scoped package; consistent with Exodus Movement's internal dependency pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Exodus SDK package; sparse README/no keywords is a style choice, not spam. | ai | |
| provenance | no-provenance | AI (provenance): Provenance explicitly disabled in publishConfig; consistent across all Exodus packages. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.30.2 | 11 / 10 | |
| 2.30.0 | 11 / 8 | |
| 2.28.1 | 11 / 8 | |
| 2.25.0 | 11 / 8 | |
| 2.24.0 | 10 / 8 | |
| 2.23.3 | 10 / 8 | |
| 2.21.0 | 8 / 9 | |
| 2.20.1 | 8 / 9 | |
| 2.20.0 | 8 / 8 | |
| 2.19.3 | 8 / 8 | |
| 2.19.0 | 8 / 8 | |
| 2.18.0 | 8 / 8 | |
| 2.17.0 | 8 / 8 | |
| 2.16.4 | 8 / 8 | |
| 2.16.2 | 8 / 8 | |
| 2.15.0 | 8 / 7 | |
| 2.14.2 | 8 / 7 | |
| 2.12.1 | 8 / 7 | |
| 2.10.0 | 8 / 6 | |
| 2.8.0 | 8 / 6 | |
| 2.7.6 | 8 / 6 |
v2.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.4
2 findingsThis version was published by a different npm account than previous versions on 2025-10-23. 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.
v2.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.