@ledgerhq/connect-kitnpm
This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →- latest 1.1.12
- last known licence MIT
- assessment attempted yesterday
- registry checked 26 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 11 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
Third-party facts checked yesterday; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-11 | first verdict: unknown |
Supply-chain history 1
-
account hijacked 2023-12 1.1.5, 1.1.6, 1.1.7
A former employee was phished and the npm account used to publish versions carrying a wallet drainer that showed a fake connect-wallet dialog in dApps.
A clean 1.1.8 followed within the hour; over $600,000 was drained in the meantime.
Source: Sonatype post-mortem and Ledger’s incident report, 14 December 2023. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@ledgerhq/connect-kit)Watch it
Get told when @ledgerhq/connect-kit changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.