@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, 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Stale Ledger-internal maintainer rotation, stable for years. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same rotation as above, not a takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change from 2022, long-stable, matches Ledger org. | ai | |
| 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 13 of 13)
| 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 | |
| 6.12.0 | 0 / 8 | |
| 6.11.0 | 0 / 8 | |
| 6.10.1 | 0 / 0 | |
| 6.10.0 | 0 / 0 | |
| 6.2.0 | 0 / 0 | |
| 6.0.2 | 0 / 0 | |
| 6.0.1 | 0 / 0 | |
| 6.0.0 | 0 / 0 |
v6.12.0
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-11-24. It has since remained available on npm for 969 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2023-11-09. It has since remained available on npm for 984 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
2 findingsThis version was published by a different npm account (sergii-shkolin) than the most recent previously approved version (gre) on 2022-09-30. It has since remained available on npm for 1389 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.