Tabby
Website
Self-hosted AI coding assistant
Is Tabby safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Tabby
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Tabby scores 49.0/100 (Grade D), ranked #987 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 99% of recent commits are signed; last pushed 2026-06-30. Every point is earned from checkable signals — never paid placement. How scoring works →
How Tabby could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.2 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Maintained 0 +10.0 → 59.0 C · #40 of 77
Chain of custody
Scanners check what the code says. This traces who ships Tabby and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/TabbyML/tabby, NOASSERTION, last pushed 2026-06-30. 99% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Oct 6, 2026). The checks that decide who can get a change released:
- Code Review8
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 9Branch-Protection 3CI-Tests 6CII-Best-Practices 0Code-Review 8Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 9Maintained 0Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Tabby is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Tabby.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Tabby’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Tabby compares in Coding Agents
- #54 Whale 50.9 +1.9
- #55 Roo Code 50.4 +1.4
- #56 Tabby 49.0 this agent
- #57 OpenCursor 48.8 −0.2
- #58 Grok CLI 46.4 −2.6
Bars show each HVTrust score; the tick marks Tabby’s 49.0.
Where the 49.0 comes from
HVTrust dimensions vs the Coding Agents average
49.0 / 100 · 100.0% confidenceTabby Coding Agents average (77 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
53.4 / 100Common questions about Tabby
Does Tabby publish package provenance?
Does Tabby have an OpenSSF Scorecard?
Is Tabby actively maintained?
What license does Tabby use?
Are Tabby's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Tabby'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.
Maintain Tabby?
For maintainers
HVTrust scores Tabby 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/tabby)
<a href="https://hvtracker.net/agents/tabby"><img src="https://hvtracker.net/badge/tabby.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON