pingcap/tidb
TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.
40.6k stars · 6.3k forks · Go
Caution
Caution: the published package has not been released in two years.
Why
- The Go package github.com/pingcap/tidb has had no release since January 2019, while the repository has 1,736 human commits in the last year; the old release has 3 known security advisories (GHSA-7fxj-fr3v-r9gj, GHSA-9g6g-xqv5-8g5w, GO-2024-3284), which do not show whether the current code is affected. (source 1, source 2, source 3, source 4, source 5)
What would change this
- A new package release is published.
- Partly checked: maintenance (Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.)
Maintenance
PartialActive
- Human commits, 30 days
- 118
- Human commits, 90 days
- 370
- Human commits, 365 days
- 1.7k
- Bot share of commits, 365 days
- 0%
- Last commit
- Oct 14, 2026 (15 hours ago)
- Last human commit
- Oct 14, 2026 (15 hours ago)
- Authors, 90 days
- 61
- Last release
- Sep 17, 2026 (28 days ago)
- Median PR merge time
- 21 hours
Responsiveness: of 14 recent issues, 64% got a maintainer reply. Median first response: under an hour.
- Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 498 since Oct 14, 2025
- Authors for half of commits
- 7
- Authors for 80% of commits
- 22
- Contributors
- 390
Top committers
- D3Hunter: 18% of commits
- flaky-claw: 10% of commits
- winoros: 5% of commits
- windtalker: 5% of commits
- 0xPoe: 5% of commits
- Shares come from the newest sampled commits, since the commit sample is capped.
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Dec 1, 2015 to Dec 1, 2015: about 32 more stars than usual, peak 37 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Dec 9, 2015 to Dec 11, 2015: about 52 more stars than usual, peak 29 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Apr 4, 2016 to Apr 5, 2016: about 58 more stars than usual, peak 41 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jun 30, 2016 to Jun 30, 2016: about 53 more stars than usual, peak 56 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Oct 25, 2016 to Oct 27, 2016: about 75 more stars than usual, peak 44 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jan 2, 2017 to Jan 4, 2017: about 301 more stars than usual, peak 240 in one day, a spike that tapers off. Outside explanation: a Hacker News post, a jump in forks.
- Jun 12, 2017 to Jun 14, 2017: about 201 more stars than usual, peak 100 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Sep 11, 2018 to Sep 13, 2018: about 107 more stars than usual, peak 58 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Nov 17, 2020 to Nov 19, 2020: about 93 more stars than usual, peak 52 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jan 6, 2025 to Jan 8, 2025: about 104 more stars than usual, peak 73 in one day, a spike that tapers off. Outside explanation: a Hacker News post, a jump in issues and pull requests.
- 2 stars GitHub has since removed (tracked since Oct 14, 2026).
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- The star history looks organic.
Sources: How star history is analyzed
Risk
CompleteFlags
- Warning: The latest release of the Go package github.com/pingcap/tidb was published more than 24 months ago, while the repository has had 1,736 human commits in the last year (deps.dev); the old release has 3 known security advisories (GHSA-7fxj-fr3v-r9gj, GHSA-9g6g-xqv5-8g5w, GO-2024-3284), which do not show whether the current code is affected. Details
License
- Now
- Apache-2.0 (OSI-approved)
- A year ago
- Apache-2.0 (OSI-approved)
Packages
- github.com/pingcap/tidb (GO): latest v2.0.11+incompatible, published Jan 3, 2019
Advisories for the latest version: GHSA-7fxj-fr3v-r9gj (critical), GHSA-9g6g-xqv5-8g5w (moderate), GO-2024-3284 (unknown)
Package and advisory data: deps.dev and OSV.
OpenSSF Scorecard: 8.2 out of 10 (via deps.dev).
Sources: GitHub: pingcap/tidb, deps.dev: Go github.com/pingcap/tidb, OSV: GHSA-7fxj-fr3v-r9gj, OSV: GHSA-9g6g-xqv5-8g5w, OSV: GO-2024-3284
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/pingcap/tidb)Earlier verdicts
- Oct 14, 2026: Caution
- Oct 14, 2026: Caution
- Oct 13, 2026: Caution
- Oct 13, 2026: Avoid