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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed 94 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
33.6k
Forks
1.7k
Last Push
2026-03-02
94 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
0
Open Issues
317
Rank Change
▼12
was #138
Analysis
HVTrust Dimensions
49.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.1 / 17
MaintenanceFreshness and commits
5.7 / 20
AdoptionStars and downloads
10.9 / 20
Activity Inputs
54.4 / 100
StarsRepository reach
27.2 / 30
FreshnessLast push recency
11.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
15.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.2 / 10
via deps.dev · OpenSSF
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
Maintained0
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.2/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?
Slowing down. Last push was 94 days ago — keep an eye on whether activity resumes.
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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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) · OSSF Scorecard via deps.dev · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
