@ledgerhq/coin-mina
Mina 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): @ledgerhq/coin-framework is a sibling package in the same LedgerHQ org/monorepo; its use as a dependency in coin integration packages is expected and stable. | ai | |
| phantom-deps | phantom-dep:expect | AI (phantom-deps): expect appears in both dependencies and devDependencies; phantom-dep flag is a false positive from config-file-only references in test setup. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a common utility; phantom-dep flag indicates config-file-only reference, benign for this package type. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-live | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/cryptoassets | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-network | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-cryptoassets | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/logs | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/ledger-wallet-framework | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/devices | AI (phantom-deps): Same-org package; phantom-dep finding is benign for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/cryptoassets | AI (phantom-deps): Same-org package; phantom-dep finding is benign for this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Large org CI publishing without Sigstore provenance is common; no other risk signals present. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-module-framework | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/errors | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai | |
| dependencies | unvetted-dep:@ledgerhq/devices | AI (dependencies): Same-org @ledgerhq scoped package from the official LedgerHQ/ledger-live monorepo; not a security risk. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.15.3 | 15 / 14 | |
| 1.15.2 | 15 / 14 | |
| 1.15.1 | 15 / 14 | |
| 1.15.0 | 15 / 14 | |
| 1.14.2 | 15 / 13 | |
| 1.14.1 | 15 / 13 | |
| 1.14.0 | 15 / 13 | |
| 1.13.0 | 15 / 12 | |
| 1.12.1 | 15 / 10 | |
| 1.12.0 | 15 / 10 | |
| 1.11.0 | 14 / 10 | |
| 1.10.0 | 14 / 10 | |
| 1.9.2 | 14 / 9 | |
| 1.9.1 | 14 / 9 | |
| 1.9.0 | 14 / 9 | |
| 1.8.2 | 14 / 9 | |
| 1.8.1 | 14 / 9 | |
| 1.8.0 | 14 / 9 | |
| 1.7.0 | 14 / 9 | |
| 1.6.0 | 14 / 8 | |
| 1.5.1 | 14 / 8 | |
| 1.5.0 | 14 / 8 | |
| 1.4.3 | 14 / 8 | |
| 1.4.2 | 14 / 8 | |
| 1.4.1 | 14 / 8 | |
| 1.4.0 | 14 / 8 | |
| 1.3.0 | 14 / 8 | |
| 1.2.3 | 14 / 8 | |
| 1.2.2 | 14 / 8 | |
| 1.2.1 | 14 / 8 | |
| 1.2.0 | 14 / 8 | |
| 1.1.17 | 14 / 8 | |
| 1.1.16 | 14 / 8 | |
| 1.1.15 | 14 / 8 | |
| 1.1.14 | 14 / 8 | |
| 1.1.13 | 14 / 8 | |
| 1.1.12 | 14 / 8 | |
| 1.1.11 | 14 / 8 | |
| 1.1.10 | 14 / 8 | |
| 1.1.9 | 14 / 8 | |
| 1.1.8 | 14 / 8 | |
| 1.1.7 | 14 / 8 | |
| 1.1.6 | 14 / 8 | |
| 1.1.5 | 14 / 8 | |
| 1.1.4 | 14 / 8 | |
| 1.1.3 | 14 / 8 | |
| 1.1.2 | 14 / 8 |
v1.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.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.
v1.12.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.
v1.12.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.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.