@ledgerhq/coin-evm
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:src/adapters/etherscan.test.ts | AI (source-diff): Long hex strings in test files are blockchain transaction input data fixtures, not malicious payloads. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(data.slice(2), 'hex') is standard EVM ABI calldata handling — stripping 0x prefix from hex-encoded Ethereum transaction data. Not obfuscation. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get(error, 'code') is a standard safe property access pattern in JS error handling, not API obfuscation. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): URL appears in an integration test file referencing Monad testnet RPC. .xyz TLDs are common in Web3/blockchain infrastructure; not a C2 indicator here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 22 / 19 | |
| 4.0.0 | 22 / 19 | |
| 3.7.0 | 22 / 19 | |
| 3.6.0 | 22 / 19 | |
| 3.5.1 | 22 / 19 | |
| 3.5.0 | 22 / 19 | |
| 3.4.0 | 22 / 19 | |
| 3.3.0 | 22 / 19 | |
| 3.2.0 | 22 / 18 | |
| 3.1.0 | 22 / 18 | |
| 3.0.0 | 21 / 18 | |
| 2.46.0 | 21 / 18 | |
| 2.45.0 | 21 / 17 | |
| 2.44.0 | 21 / 17 | |
| 2.43.0 | 21 / 17 | |
| 2.42.0 | 21 / 19 | |
| 2.41.0 | 21 / 19 | |
| 2.40.0 | 21 / 19 | |
| 2.39.0 | 21 / 19 | |
| 2.38.0 | 21 / 18 | |
| 2.37.1 | 21 / 18 | |
| 2.37.0 | 21 / 18 | |
| 2.36.1 | 21 / 18 | |
| 2.36.0 | 21 / 18 | |
| 2.35.0 | 21 / 18 | |
| 2.34.0 | 21 / 18 |
v4.1.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
2 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.