@ledgerhq/swift-bridge-hw-app-eth
Package to facilitate bundling hw-app-eth in the EthWrapper Swift package
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): LedgerHQ CI-managed package; maintainer rotation without new external additions is routine for this org. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI automation; lack of Sigstore provenance is consistent across their ecosystem and not a risk signal for this package. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.6.7 | 2 / 9 | |
| 1.6.6 | 2 / 9 | |
| 1.6.5 | 2 / 9 | |
| 1.6.4 | 2 / 9 | |
| 1.6.3 | 2 / 9 | |
| 1.6.2 | 2 / 9 | |
| 1.6.1 | 2 / 9 | |
| 1.6.0 | 2 / 9 | |
| 1.5.2 | 2 / 9 | |
| 1.5.1 | 2 / 9 | |
| 1.5.0 | 2 / 9 | |
| 1.4.0 | 2 / 9 | |
| 1.3.6 | 2 / 9 | |
| 1.3.5 | 2 / 9 | |
| 1.3.4 | 2 / 9 | |
| 1.3.3 | 2 / 9 | |
| 1.3.2 | 2 / 9 | |
| 1.3.1 | 2 / 9 | |
| 1.3.0 | 2 / 9 | |
| 1.2.55 | 2 / 8 | |
| 1.2.54 | 2 / 8 | |
| 1.2.53 | 2 / 8 | |
| 1.2.52 | 2 / 8 | |
| 1.2.51 | 2 / 8 | |
| 1.2.50 | 2 / 8 | |
| 1.2.49 | 2 / 8 | |
| 1.2.48 | 2 / 8 | |
| 1.2.47 | 2 / 8 | |
| 1.2.46 | 2 / 8 | |
| 1.2.45 | 2 / 8 | |
| 1.2.44 | 2 / 8 | |
| 1.2.43 | 2 / 8 | |
| 1.2.42 | 2 / 8 | |
| 1.2.41 | 2 / 8 | |
| 1.2.40 | 2 / 8 | |
| 1.2.39 | 2 / 8 | |
| 1.2.38 | 2 / 8 | |
| 1.2.37 | 2 / 8 | |
| 1.2.36 | 2 / 8 | |
| 1.2.35 | 2 / 8 | |
| 1.2.34 | 2 / 8 | |
| 1.2.33 | 2 / 8 | |
| 1.2.32 | 2 / 8 | |
| 1.2.31 | 2 / 8 | |
| 1.2.30 | 2 / 8 |
v1.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.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.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.