@ledgerhq/devices
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 pipeline without Sigstore provenance; consistent across their package ecosystem. Not a meaningful risk signal for this org. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 8.17.0 | 1 / 10 | |
| 8.16.0 | 1 / 10 | |
| 8.15.1 | 4 / 10 | |
| 8.15.0 | 4 / 10 | |
| 8.14.2 | 4 / 10 | |
| 8.14.1 | 4 / 10 | |
| 8.14.0 | 4 / 10 | |
| 8.13.0 | 4 / 10 | |
| 8.12.0 | 4 / 10 | |
| 8.11.0 | 4 / 10 | |
| 8.10.0 | 4 / 10 | |
| 8.9.0 | 4 / 9 | |
| 8.8.0 | 4 / 9 | |
| 8.7.1 | 4 / 9 | |
| 8.7.0 | 4 / 9 | |
| 8.6.1 | 4 / 9 | |
| 8.6.0 | 4 / 9 | |
| 8.5.1 | 4 / 9 | |
| 8.5.0 | 4 / 9 | |
| 8.4.8 | 4 / 9 | |
| 8.4.7 | 4 / 9 | |
| 8.4.6 | 4 / 9 | |
| 8.4.5 | 4 / 9 | |
| 8.4.4 | 4 / 9 | |
| 8.4.3 | 4 / 9 | |
| 8.4.2 | 4 / 9 | |
| 8.4.1 | 4 / 9 | |
| 8.4.0 | 4 / 9 | |
| 8.3.0 | 4 / 9 | |
| 8.2.2 | 4 / 9 | |
| 8.2.1 | 4 / 9 | |
| 8.2.0 | 4 / 9 | |
| 8.1.0 | 4 / 9 | |
| 8.0.8 | 4 / 9 | |
| 8.0.7 | 4 / 9 | |
| 8.0.6 | 4 / 9 | |
| 8.0.5 | 4 / 9 | |
| 8.0.4 | 4 / 9 | |
| 8.0.3 | 4 / 9 | |
| 8.0.2 | 4 / 9 | |
| 8.0.1 | 4 / 10 | |
| 8.0.0 | 4 / 1 |
v8.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.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.
v8.4.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.
v8.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
2 findingsThis version was published by a different npm account (ldg-github-ci) than the most recent previously approved version (sergii-shkolin) on 2024-02-19. It has since remained available on npm for 882 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.
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.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.
v8.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.