@ledgerhq/coin-tester-evm
Ledger EVM Coin Tester
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is declared in both dependencies and devDependencies; used via config path in scripts, not direct import. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:8545 is the standard localhost Ethereum JSON-RPC port used by Anvil/Hardhat/Ganache. Expected in EVM test tooling; not a network exfiltration risk. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env when spawning a local Anvil test node is standard practice for test harnesses. No exfiltration path; environment is passed to a local child process. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.26.0 | 13 / 10 | |
| 1.25.1 | 13 / 10 | |
| 1.25.0 | 13 / 10 | |
| 1.24.0 | 13 / 10 | |
| 1.23.1 | 13 / 10 | |
| 1.23.0 | 13 / 10 | |
| 1.22.0 | 14 / 11 | |
| 1.21.0 | 14 / 9 | |
| 1.20.0 | 14 / 9 | |
| 1.19.0 | 14 / 8 | |
| 1.18.1 | 14 / 8 | |
| 1.18.0 | 14 / 8 | |
| 1.17.2 | 14 / 8 | |
| 1.17.1 | 14 / 8 | |
| 1.17.0 | 14 / 8 | |
| 1.16.0 | 15 / 9 | |
| 1.15.0 | 15 / 9 | |
| 1.14.1 | 15 / 10 | |
| 1.14.0 | 15 / 10 | |
| 1.13.0 | 15 / 11 | |
| 1.12.2 | 14 / 11 | |
| 1.12.1 | 14 / 11 | |
| 1.12.0 | 14 / 11 | |
| 1.11.1 | 15 / 11 | |
| 1.11.0 | 15 / 11 | |
| 1.10.0 | 15 / 11 | |
| 1.1.2 | 13 / 8 |
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
7 findingsSpreading entire process.env into an object — may capture all secrets 8 | cwd, 9 | log: Boolean(process.env.DEBUG), > 10 | env: { 11 | ...process.env, 12 | RPC: rpc,
Spreading entire process.env into an object — may capture all secrets 17 | const { out } = await compose.logs("anvil", { 18 | cwd, > 19 | env: { 20 | ...process.env, 21 | RPC: rpc,
Spreading entire process.env into an object — may capture all secrets 47 | cwd, 48 | log: Boolean(process.env.DEBUG), > 49 | env: { 50 | ...process.env, 51 | RPC: rpc,
Spreading entire process.env into an object — may capture all secrets 56 | const { out } = await compose.logs("anvil", { 57 | cwd, > 58 | env: { 59 | ...process.env, 60 | RPC: rpc,
Spreading entire process.env into an object — may capture all secrets 12 | cwd, 13 | log: Boolean(process.env.DEBUG), > 14 | env: { 15 | ...process.env, 16 | RPC: rpc,
Spreading entire process.env into an object — may capture all secrets 22 | const { out } = await compose.logs("anvil", { 23 | cwd, > 24 | env: { 25 | ...process.env, 26 | RPC: rpc,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.