@ledgerhq/hw-app-str
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:tests/Str.test.ts | AI (source-diff): Long hex strings in test files are APDU command/response test vectors for Ledger hardware wallet communication — standard pattern for this package's test suite, not malicious payloads. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI automation; lack of Sigstore provenance is consistent across their ecosystem and not a security concern for this established package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/hw-transport | AI (dependencies): @ledgerhq/hw-transport is a core LedgerHQ dependency used across the entire ledger-live ecosystem; its presence here is expected and benign. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 7.7.3 | 3 / 10 | |
| 7.7.2 | 3 / 10 | |
| 7.7.1 | 3 / 10 | |
| 7.7.0 | 3 / 10 | |
| 7.6.1 | 3 / 10 | |
| 7.6.0 | 3 / 10 | |
| 7.5.0 | 3 / 10 | |
| 7.4.0 | 3 / 10 | |
| 7.3.1 | 3 / 9 | |
| 7.3.0 | 3 / 9 | |
| 7.2.10 | 3 / 9 | |
| 7.2.9 | 3 / 9 | |
| 7.2.8 | 3 / 9 | |
| 7.2.7 | 3 / 9 | |
| 7.2.6 | 3 / 9 | |
| 7.2.5 | 3 / 9 | |
| 7.2.4 | 3 / 9 | |
| 7.2.3 | 3 / 9 | |
| 7.2.2 | 3 / 10 | |
| 7.2.1 | 3 / 10 |
v7.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.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.
v7.6.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.
v7.5.0
2 findingsModified file contains 12 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
2 findingsModified file contains 12 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
2 findingsModified file contains 12 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.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.