@ledgerhq/coin-tester-polkadot
Ledger Polkadot 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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): env-spread is used to pass the parent environment to a child test process (chopsticks sidecar). Standard pattern for test harnesses; not a secret exfiltration risk in this context. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The flagged string is a localhost readiness check ('Listening on http://0.0.0.0:8080/') for a local test sidecar, not an outbound request to a raw IP. False positive for this test infrastructure package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is referenced in the start script via DOTENV_CONFIG_PATH env var; legitimate use even if not directly imported in source files. | ai | |
| phantom-deps | phantom-dep:expect | AI (phantom-deps): expect is a test assertion library used in test scenarios; phantom detection is a false positive for test-only usage patterns. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.17.3 | 14 / 11 | |
| 1.17.2 | 14 / 11 | |
| 1.17.1 | 14 / 11 | |
| 1.17.0 | 14 / 11 | |
| 1.16.0 | 14 / 11 | |
| 1.15.1 | 14 / 11 | |
| 1.15.0 | 14 / 11 | |
| 1.14.0 | 15 / 11 | |
| 1.13.0 | 15 / 9 | |
| 1.12.0 | 15 / 9 | |
| 1.11.0 | 15 / 8 | |
| 1.10.1 | 14 / 8 | |
| 1.10.0 | 14 / 8 | |
| 1.9.0 | 14 / 8 | |
| 1.8.3 | 14 / 7 | |
| 1.8.2 | 14 / 7 | |
| 1.8.1 | 14 / 7 | |
| 1.8.0 | 14 / 7 | |
| 1.7.1 | 14 / 7 | |
| 1.7.0 | 14 / 7 | |
| 1.6.0 | 14 / 6 | |
| 1.5.1 | 15 / 6 | |
| 1.5.0 | 15 / 6 | |
| 1.4.4 | 15 / 6 | |
| 1.4.3 | 15 / 6 | |
| 1.4.2 | 15 / 6 | |
| 1.4.1 | 15 / 6 | |
| 1.4.0 | 15 / 6 | |
| 1.3.6 | 15 / 6 | |
| 1.3.5 | 15 / 6 | |
| 1.3.4 | 15 / 6 | |
| 1.3.3 | 15 / 6 | |
| 1.3.2 | 15 / 6 | |
| 1.3.1 | 15 / 6 | |
| 1.3.0 | 15 / 6 | |
| 1.2.6 | 15 / 6 | |
| 1.2.5 | 15 / 6 | |
| 1.2.4 | 15 / 6 | |
| 1.2.3 | 15 / 6 | |
| 1.2.2 | 15 / 6 | |
| 1.2.1 | 15 / 6 | |
| 1.2.0 | 15 / 6 | |
| 1.1.7 | 15 / 6 | |
| 1.1.6 | 15 / 6 | |
| 1.1.5 | 15 / 6 | |
| 1.1.4 | 15 / 6 | |
| 1.1.3 | 15 / 6 | |
| 1.1.2 | 15 / 6 |
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
4 findingsSpreading entire process.env into an object — may capture all secrets 8 | cwd, 9 | log: Boolean(process.env.DEBUG), > 10 | env: { ...process.env, CHOPSTICKS_CONFIG: chopsticksConfig }, 11 | }); 12 | let chopsticksStarted = false;
Spreading entire process.env into an object — may capture all secrets 48 | cwd, 49 | log: Boolean(process.env.DEBUG), > 50 | env: { ...process.env, CHOPSTICKS_CONFIG: chopsticksConfig }, 51 | }); 52 | let chopsticksStarted = false;
Spreading entire process.env into an object — may capture all secrets 10 | cwd, 11 | log: Boolean(process.env.DEBUG), > 12 | env: { ...process.env, CHOPSTICKS_CONFIG: chopsticksConfig }, 13 | }); 14 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
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.