Crabtalk

The long-running embedded agent

Agent Frameworks Rust Listed Apache-2.0

Is Crabtalk safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.4 / 10
Provenance None
Signed commits 100%
Last push 32d ago
Compare Crabtalk
Suggest a correction

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

  1. #69 waku-agent 56.5 +2.6
  2. #70 Spring AI Alibaba 54.1 +0.2
  3. #71 Crabtalk 53.9 this agent
  4. #72 LazyLLM 53.9 ±0
  5. #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% confidence

Crabtalk Agent Frameworks average (122 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.2 / 25
0.6 below avg 9.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
1.0 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
9.9 / 20
3.9 below avg 13.8
AdoptionLog-scaled stars · package downloads
8.6 / 20
2.6 below avg 11.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 14 spots (#819 → #833)
2026-09-24
Rank Moved
Rank dropped 44 spots (#775 → #819)
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signals The repo was last pushed 32 days ago. Fresh activity helps separate stable projects from stale ones.
46.9
Activity sub-score · out of 100
#71

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 refreshed 2026-09-26 06:32 UTC · Repo last pushed 32 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
745
Forks
85
Last Push
2026-08-25
32 days ago
Commits (4 wk)
0
Downloads (7d)
18
crates.io
HN mentions (30d)
—
Open Issues
11
Rank Change
▲6
was #833

Analysis

Activity Inputs

46.9 / 100
StarsRepository reach
17.2 / 30
FreshnessLast push recency
20.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.4 / 10
OpenSSF Scorecard · scanned Sep 24, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 9
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 9
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Common questions about Crabtalk

Public trust evidence for Crabtalk 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 Crabtalk publish package provenance?
No published build provenance is currently detected for Crabtalk. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Crabtalk have an OpenSSF Scorecard?
Crabtalk has an OpenSSF Scorecard score of 3.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 Crabtalk actively maintained?
Slowing down. Last push was 32 days ago — keep an eye on whether activity resumes.
What license does Crabtalk use?
Crabtalk ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Crabtalk's commits signed?
100% of the last 100 commits to Crabtalk 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.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 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.

2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-02
Mcp Status Changed
Detected MCP server support changed: implemented → none

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
Rank 20Listed 2HVTrust 2Grade 2Scorecard 1MCP 1Surface 1License 1Delisted 1
2026-09-25
Rank Moved
Rank dropped 14 spots (#819 → #833)
2026-09-24
Rank Moved
Rank dropped 44 spots (#775 → #819)
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 245 spots (#1020 → #775)
2026-09-23
HVTrust Changed
HVTrust up 30.8pts (24.5 → 55.3)
2026-09-22
Newly Listed
First tracked at rank #1020
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 19 spots (#688 → #707)
2026-09-16
Rank Moved
Rank dropped 23 spots (#665 → #688)
2026-09-15
Rank Moved
Rank dropped 12 spots (#653 → #665)
2026-09-11
Rank Moved
Rank dropped 13 spots (#623 → #636)
2026-09-08
Rank Moved
Rank dropped 14 spots (#599 → #613)
2026-09-07
Rank Moved
Rank dropped 42 spots (#557 → #599)
2026-09-05
Rank Moved
Rank dropped 77 spots (#474 → #551)
2026-09-04
Rank Moved
Rank dropped 13 spots (#461 → #474)
2026-09-03
Rank Moved
Rank dropped 23 spots (#438 → #461)
2026-09-02
License Changed
License changed from MIT to Apache-2.0
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-02
Mcp Status Changed
Detected MCP server support changed: implemented → none
2026-09-01
Rank Moved
Rank dropped 12 spots (#435 → #447)
2026-08-31
Rank Moved
Rank dropped 32 spots (#403 → #435)
2026-08-30
Rank Moved
Rank rose 13 spots (#416 → #403)
2026-08-29
Rank Moved
Rank dropped 14 spots (#402 → #416)
2026-08-27
Rank Moved
Rank dropped 16 spots (#385 → #401)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.4/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 305 spots (#690 → #385)
2026-08-26
HVTrust Changed
HVTrust up 22.5pts (36.6 → 59.1)
2026-08-16
Rank Moved
Rank dropped 12 spots (#684 → #696)
2026-08-12
Rank Moved
Rank rose 11 spots (#695 → #684)
2026-08-10
Newly Listed
First tracked at rank #695

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/crabtalk.svg)](https://hvtracker.net/agents/crabtalk)
HTML:
<a href="https://hvtracker.net/agents/crabtalk"><img src="https://hvtracker.net/badge/crabtalk.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
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