@ledgerhq/coin-ton Apache-2.0 46 versions

@ledgerhq/coin-ton

npm Repository Homepage

Ton Coin integration

46

Versions

Apache-2.0

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

LedgerLedgerWallettonTonHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decoding is used to parse TON blockchain Cell data structures — standard operation for a TON coin integration library, not malicious payload hiding.	ai	2026/04/25
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding converts xpub public keys to Buffers for TON wallet creation — standard cryptographic operation in a blockchain integration library.	ai	2026/04/25
phantom-deps	phantom-dep:msw	AI (phantom-deps): msw (Mock Service Worker) is a test utility referenced in config files; not a runtime security concern for this package.	ai	2026/04/25
phantom-deps	phantom-dep:@ton/crypto	AI (phantom-deps): Referenced in config files for a TON blockchain integration package; legitimate transitive/config usage.	ai	2026/04/25
phantom-deps	phantom-dep:@ledgerhq/live-env	AI (phantom-deps): Same-org package from LedgerHQ; referenced in config context, not a security concern.	ai	2026/04/25

Versions (showing 46 of 46)

Version	Deps	Published
0.28.5	19 / 10	2026-06-05
0.28.4	19 / 10	2026-05-28
0.28.3	19 / 10	2026-05-21
0.28.2	19 / 10	2026-05-06
0.28.1	19 / 10	2026-05-04
0.28.0	19 / 10	2026-04-22
0.27.0	19 / 10	2026-04-15
0.26.1	19 / 8	2026-04-01
0.26.0	19 / 8	2026-03-26
0.25.0	18 / 8	2026-03-18
0.24.0	18 / 8	2026-03-12
0.23.2	18 / 7	2026-03-03
0.23.1	18 / 7	2026-02-25
0.23.0	18 / 7	2026-02-17
0.22.1	18 / 7	2026-02-10
0.22.0	18 / 7	2026-01-30
0.21.0	18 / 7	2026-01-26
0.20.0	18 / 7	2026-01-19
0.19.0	18 / 6	2026-01-13
0.18.1	18 / 6	2025-12-31
0.18.0	18 / 6	2025-12-29
0.17.2	18 / 6	2025-12-17
0.17.1	18 / 6	2025-12-08
0.17.0	18 / 6	2025-11-20
0.16.0	19 / 7	2025-11-05
0.15.0	19 / 7	2025-10-16
0.14.3	19 / 7	2025-10-01
0.14.2	19 / 7	2025-09-25
0.14.1	19 / 7	2025-09-16
0.14.0	19 / 7	2025-09-05
0.13.7	19 / 7	2025-08-27
0.13.6	19 / 7	2025-08-18
0.13.5	19 / 7	2025-08-08
0.13.4	19 / 7	2025-07-31
0.13.3	19 / 7	2025-07-23
0.13.2	19 / 7	2025-07-17
0.13.1	19 / 7	2025-07-07
0.13.0	19 / 7	2025-06-27
0.12.2	19 / 7	2025-06-20
0.12.1	19 / 7	2025-06-17
0.12.0	19 / 8	2025-06-06
0.11.0	19 / 8	2025-05-27
0.10.1	19 / 8	2025-05-20
0.10.0	19 / 8	2025-05-13
0.9.1	19 / 7	2025-04-30
0.9.0	19 / 7	2025-04-25

v0.28.5

1 finding

LOW No provenance attestation provenance

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

v0.28.4

1 finding

LOW No provenance attestation provenance

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

v0.28.3

1 finding

LOW No provenance attestation provenance

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

v0.28.2

1 finding

LOW No provenance attestation provenance

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

v0.28.1

1 finding

LOW No provenance attestation provenance

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

v0.28.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.27.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.26.1

1 finding

LOW No provenance attestation provenance

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

v0.26.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.25.0

1 finding

LOW No provenance attestation provenance

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

v0.23.2

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.21.0

1 finding

LOW No provenance attestation provenance

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

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.1

1 finding

LOW No provenance attestation provenance

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

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.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.3

1 finding

LOW No provenance attestation provenance

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

v0.14.2

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

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.7

1 finding

LOW No provenance attestation provenance

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

v0.13.6

1 finding

LOW No provenance attestation provenance

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

v0.13.5

1 finding

LOW No provenance attestation provenance

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

v0.13.4

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

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

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.2

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.