github.com/pingcap/tidb-lightningGo
- latest v4.0.11+incompatible
- licence Apache-2.0
- stars 127
- assessment attempted 4 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 →Moved
The registry still points at pingcap/tidb-lightning, which is archived with a note saying development moved to pingcap/br. The verdict above is about the new home.
Maintenance trends
Loading historical repository activity…
Signals · last 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
What the project says about itself
- Security policy — published. Source: the repository.
- Open milestones — v5.0.2 20/20 done; 5.0.4 10/10 done; v4.0.15 9/9 done; 5.0.5; v5.1.2 4/4 done. Source: the repository's milestones.
- OpenSSF Scorecard — 5 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 4 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-15 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/go/github.com/pingcap/tidb-lightning)Watch it
Get told when github.com/pingcap/tidb-lightning 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.