Crabtalk
The long-running embedded agent
Is Crabtalk safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Crabtalk
How does it stack up against its Agent Frameworks neighbours?
Pick any agent to compare →In detail: Crabtalk scores 53.9/100 (Grade C), ranked #827 of 1325 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 3.4/10; 100% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Crabtalk compares in Agent Frameworks
- #69 waku-agent 56.5 +2.6
- #70 Spring AI Alibaba 54.1 +0.2
- #71 Crabtalk 53.9 this agent
- #72 LazyLLM 53.9 ±0
- #73 openagent 53.8 −0.1
Bars show each HVTrust score; the tick marks Crabtalk’s 53.9.
Where the 53.9 comes from
HVTrust dimensions vs the Agent Frameworks average
53.9 / 100 · 100.0% confidenceCrabtalk 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
46.9 / 100Supply Chain Trust
Common questions about Crabtalk
Does Crabtalk publish package provenance?
Does Crabtalk have an OpenSSF Scorecard?
Is Crabtalk actively maintained?
What license does Crabtalk use?
Are Crabtalk'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 Crabtalk'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 Crabtalk?
For maintainers
HVTrust scores Crabtalk 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/crabtalk)
<a href="https://hvtracker.net/agents/crabtalk"><img src="https://hvtracker.net/badge/crabtalk.svg" alt="HVTrust"></a>
Other agents in Agent Frameworks
GitHub REST API (repo, commits, stars, forks, license) · crates.io (downloads) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON