@exodus/web3-ethereum-utils
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@exodus/web3-types | AI (dependencies): First-party same-org Exodus package, not truly unvetted. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): Used indirectly via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@exodus/web3-utils | AI (phantom-deps): Same-org dep, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@exodus/basic-utils | AI (phantom-deps): Same-org dep, not directly imported by design. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Standard hex-to-buffer conversion in signatures.js; no obfuscation or payload hiding, stable pattern for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.7.6 | 9 / 3 | |
| 4.7.5 | 7 / 4 | |
| 4.7.4 | 7 / 1 | |
| 4.7.3 | 7 / 1 | |
| 4.7.2 | 6 / 1 | |
| 4.7.1 | 6 / 1 | |
| 4.7.0 | 6 / 1 | |
| 4.6.0 | 6 / 1 | |
| 4.5.1 | 6 / 1 | |
| 4.5.0 | 5 / 1 | |
| 4.4.0 | 5 / 1 | |
| 4.3.1 | 6 / 1 | |
| 4.3.0 | 6 / 1 | |
| 4.2.1 | 5 / 1 | |
| 4.2.0 | 5 / 1 | |
| 4.1.0 | 5 / 1 | |
| 4.0.1 | 5 / 1 | |
| 4.0.0 | 5 / 1 |
v4.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.