@ledgerhq/hw-app-icon
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): Established @ledgerhq ecosystem package published via CI; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:bip32-path | AI (phantom-deps): bip32-path is a declared runtime dependency; phantom-dep finding reflects a packaging quirk, not a security concern for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.7.6 | 3 / 11 | |
| 1.7.5 | 3 / 11 | |
| 1.7.4 | 3 / 11 | |
| 1.7.3 | 3 / 11 | |
| 1.7.2 | 3 / 11 | |
| 1.7.1 | 3 / 11 | |
| 1.7.0 | 3 / 11 | |
| 1.6.1 | 3 / 11 | |
| 1.6.0 | 3 / 11 | |
| 1.5.0 | 3 / 11 | |
| 1.4.0 | 3 / 11 | |
| 1.3.12 | 3 / 10 | |
| 1.3.11 | 3 / 10 | |
| 1.3.10 | 3 / 10 | |
| 1.3.9 | 3 / 10 | |
| 1.3.8 | 3 / 10 | |
| 1.3.7 | 3 / 10 | |
| 1.3.6 | 3 / 10 | |
| 1.3.5 | 3 / 10 | |
| 1.3.4 | 3 / 10 | |
| 1.3.3 | 3 / 10 | |
| 1.3.2 | 3 / 11 | |
| 1.3.1 | 3 / 11 | |
| 1.3.0 | 3 / 11 | |
| 1.2.0 | 3 / 11 | |
| 1.1.2 | 3 / 10 | |
| 1.1.1 | 3 / 10 | |
| 1.1.0 | 3 / 10 |
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.