@ledgerhq/coin-module-boilerplate
Boilerplate 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:@ledgerhq/coin-framework | AI (dependencies): Same-org LedgerHQ dependency expected for a coin integration boilerplate; stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ CI publisher does not currently attach Sigstore provenance; this is consistent across their packages and not a security risk. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): invariant is explicitly declared in dependencies with a version constraint; phantom-dep finding is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/devices | AI (phantom-deps): Same-org sibling package explicitly declared in dependencies; phantom-dep finding is a false positive for this LedgerHQ monorepo package. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 4.21.1 | 11 / 13 | |
| 4.21.0 | 11 / 13 | |
| 4.20.3 | 11 / 13 | |
| 4.20.2 | 11 / 13 | |
| 4.20.1 | 11 / 13 | |
| 4.20.0 | 11 / 13 | |
| 4.19.0 | 11 / 13 | |
| 4.18.1 | 11 / 11 | |
| 4.18.0 | 11 / 11 | |
| 4.17.0 | 10 / 11 | |
| 4.16.0 | 10 / 11 | |
| 4.15.0 | 10 / 10 | |
| 4.14.1 | 10 / 10 | |
| 4.14.0 | 10 / 10 | |
| 4.13.0 | 10 / 10 | |
| 4.12.2 | 10 / 10 | |
| 4.12.1 | 10 / 10 | |
| 4.12.0 | 10 / 10 | |
| 4.11.2 | 10 / 9 | |
| 4.11.1 | 10 / 9 | |
| 4.11.0 | 10 / 9 | |
| 4.10.2 | 10 / 9 | |
| 4.10.1 | 10 / 9 | |
| 4.10.0 | 10 / 9 | |
| 4.9.0 | 10 / 9 | |
| 4.8.0 | 10 / 9 | |
| 4.7.3 | 10 / 9 | |
| 4.7.2 | 10 / 9 | |
| 4.7.1 | 10 / 9 | |
| 4.7.0 | 10 / 9 | |
| 4.6.0 | 10 / 9 | |
| 4.5.0 | 10 / 9 | |
| 4.4.0 | 10 / 9 | |
| 4.3.0 | 10 / 9 | |
| 4.2.2 | 10 / 9 | |
| 4.2.1 | 10 / 9 | |
| 4.2.0 | 10 / 9 | |
| 4.1.2 | 10 / 9 | |
| 4.1.1 | 10 / 9 | |
| 4.1.0 | 10 / 9 | |
| 4.0.5 | 10 / 10 | |
| 4.0.4 | 10 / 10 | |
| 4.0.3 | 10 / 10 | |
| 4.0.2 | 10 / 10 | |
| 4.0.1 | 10 / 10 | |
| 4.0.0 | 10 / 9 |
v4.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.
v4.0.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.