@ledgerhq/hw-app-tezos
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(rawTxHex, 'hex') is standard hex-to-buffer conversion for blockchain transaction signing; expected and benign in a hardware wallet Tezos app. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI pipeline without Sigstore provenance; consistent across all their packages and not a security concern. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 6.36.6 | 4 / 10 | |
| 6.36.5 | 4 / 10 | |
| 6.36.4 | 4 / 10 | |
| 6.36.3 | 4 / 10 | |
| 6.36.2 | 4 / 10 | |
| 6.36.1 | 4 / 10 | |
| 6.36.0 | 4 / 10 | |
| 6.35.1 | 4 / 10 | |
| 6.35.0 | 4 / 10 | |
| 6.34.0 | 4 / 10 | |
| 6.33.0 | 4 / 10 | |
| 6.32.0 | 4 / 9 | |
| 6.31.11 | 4 / 9 | |
| 6.31.10 | 4 / 9 | |
| 6.31.9 | 4 / 9 | |
| 6.31.8 | 4 / 9 | |
| 6.31.7 | 4 / 9 | |
| 6.31.6 | 4 / 9 | |
| 6.31.5 | 4 / 9 | |
| 6.31.4 | 4 / 9 | |
| 6.31.3 | 4 / 9 | |
| 6.31.2 | 4 / 10 | |
| 6.31.1 | 4 / 10 | |
| 6.31.0 | 4 / 10 | |
| 6.30.0 | 4 / 10 | |
| 6.29.4 | 4 / 9 | |
| 6.29.3 | 4 / 9 | |
| 6.29.2 | 4 / 9 | |
| 6.29.1 | 4 / 9 | |
| 6.29.0 | 4 / 9 | |
| 6.28.6 | 4 / 9 | |
| 6.28.5 | 4 / 9 | |
| 6.28.4 | 4 / 9 | |
| 6.28.3 | 4 / 9 | |
| 6.28.2 | 4 / 9 | |
| 6.28.1 | 4 / 9 | |
| 6.28.0 | 4 / 9 | |
| 6.27.20 | 4 / 9 | |
| 6.27.19 | 4 / 9 | |
| 6.27.18 | 4 / 9 | |
| 6.27.17 | 4 / 9 | |
| 6.27.16 | 4 / 9 | |
| 6.27.15 | 4 / 9 | |
| 6.27.14 | 4 / 9 | |
| 6.27.13 | 4 / 10 | |
| 6.27.12 | 4 / 1 | |
| 6.27.11 | 4 / 1 | |
| 6.27.10 | 4 / 1 | |
| 6.27.9 | 4 / 1 | |
| 6.27.8 | 4 / 1 | |
| 6.27.7 | 4 / 1 | |
| 6.27.6 | 4 / 1 | |
| 6.27.5 | 4 / 1 | |
| 6.27.4 | 4 / 1 | |
| 6.27.3 | 4 / 1 | |
| 6.27.2 | 4 / 1 | |
| 6.27.1 | 4 / 0 | |
| 6.24.1 | 4 / 0 | |
| 6.20.0 | 4 / 0 | |
| 6.19.0 | 4 / 0 | |
| 6.11.2 | 4 / 0 | |
| 6.11.0 | 4 / 0 | |
| 6.10.0 | 4 / 0 | |
| 6.7.0 | 4 / 0 | |
| 6.6.1 | 4 / 0 | |
| 6.3.0 | 4 / 0 | |
| 6.2.0 | 4 / 0 | |
| 6.1.0 | 4 / 0 | |
| 6.0.2 | 4 / 0 | |
| 6.0.1 | 4 / 0 | |
| 6.0.0 | 4 / 0 |
v6.36.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.36.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.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.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.16
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.3
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-08-31. It has since remained available on npm for 1420 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.27.2
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (juan-cortes) on 2022-07-28. It has since remained available on npm for 1454 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.27.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (juan-cortes) than the most recent previously approved version (gre) on 2022-04-13, but juan-cortes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.