@exodus/basemainnet-plugin
Base Mainnet 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 Movement migrated publishing to GitHub Actions CI; consistent across their package ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal SDK plugin from Exodus Movement; sparse README/keywords are expected for org-internal packages. | ai | |
| provenance | no-provenance | AI (provenance): publishConfig explicitly sets provenance:false; intentional org policy, not an oversight. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.10.2 | 2 / 3 | |
| 2.10.1 | 2 / 3 | |
| 2.10.0 | 2 / 3 | |
| 2.9.0 | 2 / 2 | |
| 2.8.0 | 2 / 2 | |
| 2.7.3 | 2 / 2 | |
| 2.7.2 | 2 / 2 | |
| 2.7.1 | 2 / 2 | |
| 2.7.0 | 2 / 2 | |
| 2.6.0 | 2 / 2 | |
| 2.5.0 | 2 / 1 | |
| 2.4.2 | 2 / 1 | |
| 2.4.1 | 2 / 1 | |
| 2.4.0 | 2 / 1 |
v2.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.9.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. 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.7.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-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.
v2.7.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. 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.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.