@ledgerhq/coin-canton
Canton 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:protobufjs | AI (dependencies): protobufjs is a well-known library; its use is expected in a Canton blockchain integration that relies on protobuf for transaction serialization. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in this package is standard binary data deserialization for Canton blockchain transaction seeds via protobuf — not obfuscation or exfiltration. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-framework | AI (dependencies): First-party LedgerHQ dependency from the same monorepo; unvetted status is a pipeline artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): invariant is declared as a runtime dependency and used transitively; phantom-dep flag is a packaging artifact, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/devices | AI (phantom-deps): @ledgerhq/devices is a same-org dependency declared in package.json; phantom classification is a packaging artifact, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI automation (ldg-github-ci); lack of Sigstore provenance is common and not a disqualifier for this established org package. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 13 / 14 | |
| 0.25.0 | 13 / 14 | |
| 0.24.1 | 13 / 14 | |
| 0.24.0 | 13 / 14 | |
| 0.23.2 | 13 / 14 | |
| 0.23.1 | 13 / 14 | |
| 0.23.0 | 13 / 14 | |
| 0.22.0 | 13 / 14 | |
| 0.21.1 | 13 / 12 | |
| 0.21.0 | 13 / 12 | |
| 0.20.0 | 12 / 12 | |
| 0.19.0 | 12 / 12 | |
| 0.18.0 | 12 / 11 | |
| 0.17.1 | 12 / 11 | |
| 0.17.0 | 12 / 11 | |
| 0.16.0 | 12 / 11 | |
| 0.15.0 | 12 / 11 | |
| 0.14.1 | 12 / 11 | |
| 0.14.0 | 12 / 11 | |
| 0.13.0 | 12 / 10 | |
| 0.12.1 | 12 / 10 | |
| 0.12.0 | 12 / 10 | |
| 0.11.1 | 12 / 10 | |
| 0.11.0 | 12 / 10 | |
| 0.10.0 | 12 / 10 | |
| 0.9.0 | 12 / 10 | |
| 0.8.0 | 11 / 9 | |
| 0.7.0 | 10 / 9 | |
| 0.6.0 | 10 / 9 | |
| 0.5.0 | 10 / 9 | |
| 0.4.0 | 10 / 9 | |
| 0.3.0 | 10 / 9 | |
| 0.2.1 | 10 / 9 | |
| 0.2.0 | 10 / 9 |
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.