@ledgerhq/coin-icon
Ledger Icon 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 — 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:icon-sdk-js | AI (dependencies): icon-sdk-js is the official ICON blockchain SDK; its use in a Ledger ICON coin integration module is expected and appropriate across all versions. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-framework | AI (dependencies): First-party Ledger HQ dependency from the same org; its use in any @ledgerhq/* coin module is expected and stable. | ai | |
| dependencies | unvetted-dep:@ledgerhq/devices | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-env | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-live | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/cryptoassets | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-network | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-promise | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/logs | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-module-framework | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/ledger-wallet-framework | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/live-env | AI (phantom-deps): Same-org package; phantom dep pattern is expected in monorepo setups where deps are declared but used indirectly. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/live-promise | AI (phantom-deps): Same-org package; phantom dep pattern is expected in monorepo setups where deps are declared but used indirectly. | ai | |
| phantom-deps | phantom-dep:prando | AI (phantom-deps): prando is a legitimate PRNG library; phantom dep in config/test context is benign for this package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-cryptoassets | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/errors | AI (dependencies): Same-org @ledgerhq scoped package from the ledger-live monorepo; unvetted status is a registry artifact, not a risk signal. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.23.3 | 18 / 10 | |
| 0.23.2 | 18 / 10 | |
| 0.23.1 | 18 / 10 | |
| 0.23.0 | 19 / 10 | |
| 0.22.2 | 19 / 10 | |
| 0.22.1 | 19 / 10 | |
| 0.22.0 | 19 / 10 | |
| 0.21.0 | 19 / 10 | |
| 0.20.1 | 19 / 8 | |
| 0.20.0 | 19 / 8 | |
| 0.19.0 | 18 / 8 | |
| 0.18.0 | 18 / 8 | |
| 0.17.6 | 18 / 7 | |
| 0.17.5 | 18 / 7 | |
| 0.17.4 | 18 / 7 | |
| 0.17.3 | 18 / 7 | |
| 0.17.2 | 18 / 7 | |
| 0.17.1 | 18 / 7 | |
| 0.17.0 | 18 / 7 | |
| 0.16.2 | 18 / 6 | |
| 0.16.1 | 18 / 6 | |
| 0.16.0 | 18 / 6 | |
| 0.15.2 | 18 / 6 | |
| 0.15.1 | 18 / 6 | |
| 0.15.0 | 18 / 6 | |
| 0.14.0 | 18 / 6 | |
| 0.13.0 | 18 / 6 | |
| 0.12.3 | 18 / 6 | |
| 0.12.2 | 18 / 6 | |
| 0.12.1 | 18 / 6 | |
| 0.12.0 | 18 / 6 | |
| 0.11.5 | 18 / 6 | |
| 0.11.4 | 18 / 6 | |
| 0.11.3 | 18 / 6 | |
| 0.11.2 | 18 / 6 | |
| 0.11.1 | 18 / 6 | |
| 0.11.0 | 18 / 6 | |
| 0.10.12 | 18 / 6 | |
| 0.10.11 | 18 / 6 | |
| 0.10.10 | 18 / 6 | |
| 0.10.9 | 18 / 6 | |
| 0.10.8 | 18 / 7 | |
| 0.10.7 | 18 / 7 | |
| 0.10.6 | 18 / 7 | |
| 0.10.5 | 18 / 7 | |
| 0.10.4 | 18 / 6 | |
| 0.10.3 | 18 / 6 |
v0.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.