@ledgerhq/logs
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @ledgerhq/logs is a scoped package from the official LedgerHQ org; Levenshtein match to 'cors' is a coincidental string similarity with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:log4js | AI (typosquat): @ledgerhq/logs is a scoped package from the official LedgerHQ org; Levenshtein match to 'log4js' is a coincidental string similarity with no impersonation intent. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.17.0 | 0 / 9 | |
| 6.16.0 | 0 / 9 | |
| 6.15.0 | 0 / 9 | |
| 6.14.0 | 0 / 9 | |
| 6.13.0 | 0 / 8 |
v6.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.