@exodus/ethereum-meta
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal metadata package from Exodus Movement; sparse README and no keywords are expected for org-internal libs. | ai | |
| provenance | no-provenance | AI (provenance): publishConfig explicitly sets provenance:false; intentional org policy, not a red flag. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.12.0 | 2 / 3 | |
| 2.11.0 | 2 / 3 | |
| 2.10.0 | 2 / 3 | |
| 2.9.1 | 1 / 3 | |
| 2.9.0 | 1 / 3 | |
| 2.8.4 | 1 / 3 | |
| 2.8.3 | 1 / 3 | |
| 2.8.2 | 1 / 3 | |
| 2.8.1 | 1 / 3 |
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.
v2.10.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.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.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.
v2.8.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.
v2.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.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.