@ledgerhq/coin-hedera Apache-2.0 47 versions

@ledgerhq/coin-hedera

npm Repository Homepage

Ledger Hedera Coin integration

47

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

LedgerLedgerWallethbarHederaHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:expect	AI (phantom-deps): expect is a test dependency declared in package.json; phantom-dep flag is a false positive for test utilities.	ai	2026/04/27
phantom-deps	phantom-dep:lodash	AI (phantom-deps): lodash is declared in dependencies and used in config/utility contexts; legitimate dependency, not hidden.	ai	2026/04/27
phantom-deps	phantom-dep:@ledgerhq/devices	AI (phantom-deps): Same-org scoped dependency properly declared; phantom-dep flag is a false positive for internal org dependencies.	ai	2026/04/27
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decoding is used for cryptographic signature deserialization in a blockchain wallet library — expected and benign for this package.	ai	2026/04/25
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding is used to deserialize Hedera SDK transactions — standard blockchain serialization, not a malicious payload pattern.	ai	2026/04/25

Versions (showing 47 of 47)

Version	Deps	Published
1.33.0	18 / 11	2026-06-05
1.32.0	18 / 11	2026-05-28
1.31.1	18 / 11	2026-05-21
1.31.0	18 / 11	2026-05-13
1.30.1	18 / 11	2026-05-06
1.30.0	18 / 11	2026-05-04
1.29.0	18 / 11	2026-04-22
1.28.0	18 / 11	2026-04-15
1.27.0	18 / 10	2026-04-01
1.26.0	18 / 10	2026-03-26
1.25.0	17 / 10	2026-03-18
1.24.0	17 / 10	2026-03-12
1.23.0	16 / 9	2026-03-03
1.22.1	16 / 9	2026-02-25
1.22.0	16 / 9	2026-02-17
1.21.0	16 / 9	2026-02-10
1.20.0	16 / 9	2026-01-30
1.19.0	16 / 9	2026-01-26
1.18.0	16 / 9	2026-01-19
1.17.0	16 / 8	2026-01-13
1.16.1	16 / 8	2025-12-31
1.16.0	16 / 8	2025-12-29
1.15.1	15 / 8	2025-12-17
1.15.0	15 / 8	2025-12-08
1.14.0	14 / 8	2025-11-20
1.13.0	15 / 9	2025-11-05
1.12.0	15 / 9	2025-10-16
1.11.3	15 / 9	2025-10-01
1.11.2	15 / 9	2025-09-25
1.11.1	15 / 9	2025-09-16
1.11.0	15 / 9	2025-09-05
1.10.1	14 / 8	2025-08-27
1.10.0	14 / 8	2025-08-18
1.9.2	14 / 8	2025-08-08
1.9.1	14 / 8	2025-07-31
1.9.0	14 / 8	2025-07-23
1.8.2	14 / 7	2025-07-17
1.8.1	14 / 7	2025-07-07
1.8.0	14 / 7	2025-06-27
1.7.2	14 / 7	2025-06-20
1.7.1	14 / 7	2025-06-17
1.7.0	14 / 8	2025-06-06
1.6.7	14 / 7	2025-05-27
1.6.6	14 / 7	2025-05-20
1.6.5	14 / 7	2025-05-13
1.6.4	14 / 6	2025-04-30
1.6.3	14 / 6	2025-04-25

v1.33.0

1 finding

LOW No provenance attestation provenance

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

v1.32.0

1 finding

LOW No provenance attestation provenance

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

v1.31.1

1 finding

LOW No provenance attestation provenance

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

v1.31.0

1 finding

LOW No provenance attestation provenance

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

v1.30.1

1 finding

LOW No provenance attestation provenance

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

v1.30.0

1 finding

LOW No provenance attestation provenance

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

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

v1.28.0

1 finding

LOW No provenance attestation provenance

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

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

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.3

1 finding

LOW No provenance attestation provenance

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

v1.11.2

1 finding

LOW No provenance attestation provenance

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

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.2

1 finding

LOW No provenance attestation provenance

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

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.2

1 finding

LOW No provenance attestation provenance

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

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.7

1 finding

LOW No provenance attestation provenance

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

v1.6.6

1 finding

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

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.