@ledgerhq/hw-app-near
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI without Sigstore provenance; this is consistent across their package ecosystem and not a risk indicator for this well-established publisher. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 6.35.6 | 2 / 10 | |
| 6.35.5 | 2 / 10 | |
| 6.35.4 | 2 / 10 | |
| 6.35.3 | 2 / 10 | |
| 6.35.2 | 2 / 10 | |
| 6.35.1 | 2 / 10 | |
| 6.35.0 | 2 / 10 | |
| 6.34.1 | 2 / 10 | |
| 6.34.0 | 2 / 10 | |
| 6.33.0 | 2 / 10 | |
| 6.32.0 | 2 / 10 | |
| 6.31.12 | 2 / 9 | |
| 6.31.11 | 2 / 9 | |
| 6.31.10 | 2 / 9 | |
| 6.31.9 | 2 / 9 | |
| 6.31.8 | 2 / 9 | |
| 6.31.7 | 2 / 9 | |
| 6.31.6 | 2 / 9 | |
| 6.31.5 | 2 / 9 | |
| 6.31.4 | 2 / 9 | |
| 6.31.3 | 2 / 9 | |
| 6.31.2 | 2 / 10 | |
| 6.31.1 | 2 / 10 | |
| 6.31.0 | 2 / 10 | |
| 6.30.0 | 2 / 10 | |
| 6.29.4 | 2 / 9 | |
| 6.29.3 | 2 / 9 | |
| 6.29.2 | 2 / 9 | |
| 6.29.1 | 2 / 9 | |
| 6.29.0 | 2 / 9 | |
| 6.28.8 | 2 / 9 | |
| 6.28.7 | 2 / 9 | |
| 6.28.6 | 2 / 9 | |
| 6.28.5 | 2 / 9 | |
| 6.28.4 | 2 / 9 | |
| 6.28.3 | 2 / 9 | |
| 6.28.2 | 2 / 9 | |
| 6.28.1 | 2 / 9 | |
| 6.28.0 | 2 / 9 | |
| 6.27.15 | 2 / 9 | |
| 6.27.14 | 3 / 9 | |
| 6.27.13 | 3 / 9 | |
| 6.27.12 | 3 / 9 | |
| 6.27.11 | 3 / 9 | |
| 6.27.10 | 3 / 9 | |
| 6.27.9 | 3 / 9 | |
| 6.27.8 | 3 / 10 | |
| 6.27.7 | 3 / 1 | |
| 6.27.6 | 3 / 1 | |
| 6.27.5 | 3 / 1 | |
| 6.27.4 | 3 / 1 | |
| 6.27.3 | 3 / 1 |
v6.35.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.35.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.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.
v6.28.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.28.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.2
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-01-23. It has since remained available on npm for 910 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.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.
v6.27.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.