@ledgerhq/coin-near
Near 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 LedgerHQ package from the same ledger-live monorepo; unvetted flag is a false positive for this well-established ecosystem. | ai | |
| dependencies | unvetted-dep:@ledgerhq/errors | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/devices | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-live | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/cryptoassets | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-network | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/logs | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-module-framework | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/ledger-wallet-framework | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:near-api-js | AI (dependencies): Official NEAR Protocol JavaScript API library; well-known ecosystem package appropriate for a NEAR coin integration module. | ai | |
| provenance | no-provenance | AI (provenance): Ledger publishes via CI automation (ldg-github-ci); lack of Sigstore provenance is common and not a security concern for this established package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-cryptoassets | AI (dependencies): First-party @ledgerhq package from the same LedgerHQ monorepo; unvetted status is a pipeline gap, not a security concern. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.25.6 | 15 / 11 | |
| 0.25.5 | 15 / 11 | |
| 0.25.4 | 15 / 11 | |
| 0.25.3 | 15 / 11 | |
| 0.25.2 | 15 / 11 | |
| 0.25.1 | 15 / 11 | |
| 0.25.0 | 15 / 11 | |
| 0.24.0 | 15 / 11 | |
| 0.23.0 | 15 / 9 | |
| 0.22.0 | 15 / 9 | |
| 0.21.0 | 14 / 9 | |
| 0.20.0 | 14 / 9 | |
| 0.19.6 | 14 / 8 | |
| 0.19.5 | 14 / 8 | |
| 0.19.4 | 14 / 8 | |
| 0.19.3 | 14 / 8 | |
| 0.19.2 | 14 / 8 | |
| 0.19.1 | 14 / 8 | |
| 0.19.0 | 14 / 8 | |
| 0.18.0 | 14 / 7 | |
| 0.17.1 | 14 / 7 | |
| 0.17.0 | 14 / 7 | |
| 0.16.2 | 14 / 7 | |
| 0.16.1 | 14 / 7 | |
| 0.16.0 | 14 / 7 | |
| 0.15.0 | 14 / 7 | |
| 0.14.0 | 14 / 7 | |
| 0.13.3 | 14 / 7 | |
| 0.13.2 | 14 / 7 | |
| 0.13.1 | 14 / 7 | |
| 0.13.0 | 14 / 7 | |
| 0.12.1 | 14 / 7 | |
| 0.12.0 | 14 / 7 | |
| 0.11.16 | 14 / 7 | |
| 0.11.15 | 14 / 7 | |
| 0.11.14 | 14 / 7 | |
| 0.11.13 | 14 / 7 | |
| 0.11.12 | 14 / 7 | |
| 0.11.11 | 14 / 7 | |
| 0.11.10 | 14 / 7 | |
| 0.11.9 | 14 / 7 | |
| 0.11.8 | 14 / 8 | |
| 0.11.7 | 14 / 8 | |
| 0.11.6 | 14 / 8 | |
| 0.11.5 | 14 / 8 | |
| 0.11.4 | 14 / 7 | |
| 0.11.3 | 14 / 7 |
v0.25.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.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.23.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.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.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.
v0.11.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.
v0.11.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.