updated 2026-08-19 05:02 UTC

Tidb

pingcap/tidb

TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, a

Memory & Knowledge Go Grade B Listed Apache-2.0
71.5/100
Rank #128 of 1308
Compare Tidb

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-19 · 0d ago
Recent change
Rank +3

Is Tidb safe? Tidb scores 71.5/100 (Grade B), ranked #128 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.8/10; 100% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#12 Milvus — 73.4 (B) → #13 RAGFlow — 72.0 (B) → #15 Qdrant — 71.3 (B) → #16 Cognee — 69.0 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-18
Rank Moved
Rank rose 39 spots (#159 → #120)
2026-08-18
HVTrust Changed
HVTrust up 3.0pts (68.5 → 71.5)
2026-08-17
Rank Moved
Rank dropped 30 spots (#129 → #159)
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Tidb View Memory & Knowledge Report missing data
95.2
Activity sub-score · out of 100
#14
In Memory & Knowledge

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
40.4k
Forks
6.2k
Last Push
2026-08-19
today
Commits (4 wk)
119
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
5195
Rank Change
▼8
was #120

Analysis

HVTrust Dimensions vs Memory & Knowledge

71.5 / 100 · 100.0% confidence

Tidb Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.8 / 25
4.9 above avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
15.1 / 17
2.7 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.3 above avg 17.7
AdoptionLog-scaled stars · package downloads
11.1 / 20
2.5 below avg 13.6

Activity Inputs

95.2 / 100
StarsRepository reach
27.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
7.8 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 9
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 10
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 10
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 0

Is Tidb safe?

Tidb has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Tidb publish package provenance?
No published build provenance is currently detected for Tidb. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Tidb have an OpenSSF Scorecard?
Tidb has an OpenSSF Scorecard score of 7.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Tidb actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Tidb use?
Tidb ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Tidb's commits signed?
100% of the last 100 commits to Tidb are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Tidb's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-06-01
Activity Resumed
Activity resumed

Maintain Tidb?

For maintainers

HVTrust scores Tidb from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 5HVTrust 3Listed 1Score 1Grade 1Fresh 1Scorecard 1
2026-08-18
Rank Moved
Rank rose 39 spots (#159 → #120)
2026-08-18
HVTrust Changed
HVTrust up 3.0pts (68.5 → 71.5)
2026-08-17
Rank Moved
Rank dropped 30 spots (#129 → #159)
2026-08-17
HVTrust Changed
HVTrust down 3.0pts (71.5 → 68.5)
2026-08-08
Rank Moved
Rank dropped 11 spots (#107 → #118)
2026-07-01
Rank Moved
Rank rose 11 spots (#84 → #73)
2026-06-01
Scorecard Added
OSSF Scorecard: 6.7/10
2026-06-01
Activity Resumed
Activity resumed
2026-06-01
Grade Changed
Trust grade D → B
2026-06-01
Rank Moved
Rank rose 118 spots (#177 → #59)
2026-06-01
HVTrust Changed
HVTrust up 69.4pts (0.0 → 69.4)
2026-06-01
Activity Score Changed
Activity score up 95pts (0 → 95)
2026-05-31
Newly Listed
First tracked at rank #177
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 71.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/tidb.svg)](https://hvtracker.net/agents/tidb)
HTML:
<a href="https://hvtracker.net/agents/tidb"><img src="https://hvtracker.net/badge/tidb.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON