@ledgerhq/coin-hedera
Ledger Hedera Coin integration
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
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 | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is declared in dependencies and used in config/utility contexts; legitimate dependency, not hidden. | ai | |
| 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 | |
| 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 | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used to deserialize Hedera SDK transactions — standard blockchain serialization, not a malicious payload pattern. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 1.39.0 | 16 / 13 | |
| 1.38.0 | 17 / 12 | |
| 1.37.0 | 18 / 11 | |
| 1.36.0 | 18 / 11 | |
| 1.35.0 | 18 / 11 | |
| 1.34.0 | 18 / 11 | |
| 1.33.0 | 18 / 11 | |
| 1.32.0 | 18 / 11 | |
| 1.31.1 | 18 / 11 | |
| 1.31.0 | 18 / 11 | |
| 1.30.1 | 18 / 11 | |
| 1.30.0 | 18 / 11 | |
| 1.29.0 | 18 / 11 | |
| 1.28.0 | 18 / 11 | |
| 1.27.0 | 18 / 10 | |
| 1.26.0 | 18 / 10 | |
| 1.25.0 | 17 / 10 | |
| 1.24.0 | 17 / 10 | |
| 1.23.0 | 16 / 9 | |
| 1.22.1 | 16 / 9 | |
| 1.22.0 | 16 / 9 | |
| 1.21.0 | 16 / 9 | |
| 1.20.0 | 16 / 9 | |
| 1.19.0 | 16 / 9 | |
| 1.18.0 | 16 / 9 | |
| 1.17.0 | 16 / 8 | |
| 1.16.1 | 16 / 8 | |
| 1.16.0 | 16 / 8 | |
| 1.15.1 | 15 / 8 | |
| 1.15.0 | 15 / 8 | |
| 1.14.0 | 14 / 8 | |
| 1.13.0 | 15 / 9 | |
| 1.12.0 | 15 / 9 | |
| 1.11.3 | 15 / 9 | |
| 1.11.2 | 15 / 9 | |
| 1.11.1 | 15 / 9 | |
| 1.11.0 | 15 / 9 | |
| 1.10.1 | 14 / 8 | |
| 1.10.0 | 14 / 8 | |
| 1.9.2 | 14 / 8 | |
| 1.9.1 | 14 / 8 | |
| 1.9.0 | 14 / 8 | |
| 1.8.2 | 14 / 7 | |
| 1.8.1 | 14 / 7 | |
| 1.8.0 | 14 / 7 | |
| 1.7.2 | 14 / 7 | |
| 1.7.1 | 14 / 7 | |
| 1.7.0 | 14 / 8 | |
| 1.6.7 | 14 / 7 | |
| 1.6.6 | 14 / 7 | |
| 1.6.5 | 14 / 7 | |
| 1.6.4 | 14 / 6 | |
| 1.6.3 | 14 / 6 | |
| 1.6.2 | 14 / 6 | |
| 1.6.1 | 14 / 6 | |
| 1.6.0 | 14 / 6 | |
| 1.5.0 | 14 / 6 | |
| 1.4.1 | 14 / 5 | |
| 1.4.0 | 14 / 5 | |
| 1.3.7 | 14 / 5 | |
| 1.3.6 | 14 / 5 | |
| 1.3.5 | 14 / 5 | |
| 1.3.4 | 14 / 5 | |
| 1.3.3 | 14 / 5 | |
| 1.3.2 | 14 / 5 | |
| 1.3.1 | 14 / 5 | |
| 1.3.0 | 14 / 5 | |
| 1.2.1 | 14 / 5 | |
| 1.2.0 | 14 / 5 | |
| 1.1.3 | 14 / 5 | |
| 1.1.2 | 14 / 5 | |
| 1.1.1 | 14 / 5 | |
| 1.1.0 | 14 / 5 |
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
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.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.