Zeroclaw
Fast, small, and fully autonomous AI personal assistant infrastructure, any OS, any platform — deploy anywhere, swap anything 🦀
Is Zeroclaw safe? Promising trust profile, but some evidence still deserves review.
Compare Zeroclaw
How does it stack up against its Agent Frameworks neighbours?
Pick any agent to compare →In detail: Zeroclaw scores 70.4/100 (Grade B), ranked #326 of 1325 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.4/10; 100% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Zeroclaw compares in Agent Frameworks
- #20 BeeAI Framework 71.3 +0.9
- #21 AutoGen 70.5 +0.1
- #22 Zeroclaw 70.4 this agent
- #23 AgentScope 70.3 −0.1
- #24 Google ADK (Go) 69.0 −1.4
Bars show each HVTrust score; the tick marks Zeroclaw’s 70.4.
Where the 70.4 comes from
HVTrust dimensions vs the Agent Frameworks average
70.4 / 100 · 100.0% confidenceZeroclaw Agent Frameworks average (122 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
94.3 / 100Supply Chain Trust
Common questions about Zeroclaw
Does Zeroclaw publish package provenance?
Does Zeroclaw have an OpenSSF Scorecard?
Is Zeroclaw actively maintained?
What license does Zeroclaw use?
Are Zeroclaw'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 Zeroclaw'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 Zeroclaw?
For maintainers
HVTrust scores Zeroclaw 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/zeroclaw)
<a href="https://hvtracker.net/agents/zeroclaw"><img src="https://hvtracker.net/badge/zeroclaw.svg" alt="HVTrust"></a>
Other agents in Agent Frameworks
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