Is Tabby safe?
Tabby scores 54.5/100 (Grade C), ranked #209 of 328 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.4/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 →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
54.5/100 · Grade C
Strongest Signal
Transparency
12.2/17
Weakest Signal
Safety / Integrity
10.5/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-30
Activity Resumed
Activity resumed
2026-06-30
Grade Changed
Trust grade D → C
2026-06-30
Rank Moved
Rank rose 48 spots (#245 → #197)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed 11 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
33.7k
Forks
1.8k
Last Push
2026-06-30
11 days ago
Commits (4 wk)
1
Downloads (7d)
—
HN mentions (30d)
0
Open Issues
257
Rank Change
=
was #209
Analysis
HVTrust Dimensions
54.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.2 / 17
MaintenanceFreshness and commits
12.5 / 20
AdoptionStars and downloads
10.9 / 20
Activity Inputs
69.7 / 100
StarsRepository reach
27.2 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
15.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.4 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
99%
of last 100 commits verified
Binary-Artifacts9
Branch-Protection3
CI-Tests8
CII-Best-Practices0
Code-Review8
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License9
Maintained2
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Tabby safe?
Public trust evidence for Tabby is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Tabby publish package provenance?
No published build provenance is currently detected for Tabby. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Tabby have an OpenSSF Scorecard?
Tabby has an OpenSSF Scorecard score of 4.4/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 Tabby actively maintained?
Maintained. Last push was 11 days ago.
What license does Tabby use?
Tabby ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Tabby's commits signed?
99% of the last 100 commits to Tabby 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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
code
database
filesystem
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 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.
Runtime surface grew — new detected provider dependencies: OpenAI, Redis
2026-05-31
Activity Went Stale
No commits for 90 days
Maintain Tabby?
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.
Data sources
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.2 · Raw JSON
