← Home

@ledgerhq/coin-tester

npm Repository Homepage
21
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

phenry-ledgersergii-shkolingbrahm-ledgerthomas.coudrayldg-github-civbouzonledger-releaser

Keywords

LedgerLedgerWalletevmEthereumHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): 127.0.0.1 is the local Speculos API endpoint; localhost raw-IP is expected in hardware-wallet test tooling. ai
semgrep semgrep:env-spread AI (semgrep): Speculos emulator harness legitimately passes process.env to child process; stable testing pattern for this package. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep heuristic fires on config-only references, stable false positive here. ai

Versions (showing 21 of 21)

Version Deps Published
0.20.0 4 / 10
0.19.0 4 / 8
0.18.0 4 / 8
0.17.0 4 / 8
0.16.0 8 / 8
0.15.0 8 / 7
0.14.0 8 / 7
0.13.1 8 / 7
0.12.0 7 / 7
0.11.0 7 / 7
0.10.1 7 / 7
0.10.0 7 / 7
0.9.3 7 / 7
0.9.2 7 / 7
0.9.1 7 / 7
0.9.0 7 / 7
0.8.0 7 / 7
0.7.1 7 / 7
0.7.0 7 / 7
0.6.0 7 / 7
0.5.1 6 / 7

v0.18.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.0

4 findings
HIGH env-spread: lib-es/signers/speculos.js:60 semgrep

Spreading entire process.env into an object — may capture all secrets 58 | cwd, 59 | log: Boolean(process.env.DEBUG), > 60 | env: { 61 | ...process.env, 62 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: lib/signers/speculos.js:93 semgrep

Spreading entire process.env into an object — may capture all secrets 91 | cwd, 92 | log: Boolean(process.env.DEBUG), > 93 | env: { 94 | ...process.env, 95 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: src/signers/speculos.ts:87 semgrep

Spreading entire process.env into an object — may capture all secrets 85 | cwd, 86 | log: Boolean(process.env.DEBUG), > 87 | env: { 88 | ...process.env, 89 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.0

4 findings
HIGH env-spread: lib-es/signers/speculos.js:60 semgrep

Spreading entire process.env into an object — may capture all secrets 58 | cwd, 59 | log: Boolean(process.env.DEBUG), > 60 | env: { 61 | ...process.env, 62 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: lib/signers/speculos.js:93 semgrep

Spreading entire process.env into an object — may capture all secrets 91 | cwd, 92 | log: Boolean(process.env.DEBUG), > 93 | env: { 94 | ...process.env, 95 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: src/signers/speculos.ts:87 semgrep

Spreading entire process.env into an object — may capture all secrets 85 | cwd, 86 | log: Boolean(process.env.DEBUG), > 87 | env: { 88 | ...process.env, 89 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.1

4 findings
HIGH env-spread: lib-es/signers/speculos.js:60 semgrep

Spreading entire process.env into an object — may capture all secrets 58 | cwd, 59 | log: Boolean(process.env.DEBUG), > 60 | env: { 61 | ...process.env, 62 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: lib/signers/speculos.js:93 semgrep

Spreading entire process.env into an object — may capture all secrets 91 | cwd, 92 | log: Boolean(process.env.DEBUG), > 93 | env: { 94 | ...process.env, 95 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: src/signers/speculos.ts:87 semgrep

Spreading entire process.env into an object — may capture all secrets 85 | cwd, 86 | log: Boolean(process.env.DEBUG), > 87 | env: { 88 | ...process.env, 89 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

4 findings
HIGH env-spread: lib-es/signers/speculos.js:59 semgrep

Spreading entire process.env into an object — may capture all secrets 57 | cwd, 58 | log: Boolean(process.env.DEBUG), > 59 | env: { 60 | ...process.env, 61 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: lib/signers/speculos.js:92 semgrep

Spreading entire process.env into an object — may capture all secrets 90 | cwd, 91 | log: Boolean(process.env.DEBUG), > 92 | env: { 93 | ...process.env, 94 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

HIGH env-spread: src/signers/speculos.ts:86 semgrep

Spreading entire process.env into an object — may capture all secrets 84 | cwd, 85 | log: Boolean(process.env.DEBUG), > 86 | env: { 87 | ...process.env, 88 | SPECULOS_EXTRA_ARGS: libraryArgs.join(" "),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.