Rakazo
Website
Open-source Grok Bot alternative. Choose your own model and sandbox.
Is Rakazo safe? Promising trust profile, but some evidence still deserves review.
Compare Rakazo
How does it stack up against its Multi-Agent Systems neighbours?
Pick any agent to compare →In detail: Rakazo scores 64.5/100 (Grade C), ranked #494 of 1343 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 5.5/10; 100% of recent commits are signed; last pushed 2026-10-01. Every point is earned from checkable signals — never paid placement. How scoring works →
How Rakazo could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 5.5 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Maintained 0 +7.2 → 71.7 B · #3 of 41
How Rakazo compares in Multi-Agent Systems
- #8 agent-swarm 65.2 +0.7
- #9 Ruflo 64.5 ±0
- #10 Rakazo 64.5 this agent
- #11 Agency Agents 64.1 −0.4
- #12 Open Multi-Agent 61.3 −3.2
Bars show each HVTrust score; the tick marks Rakazo’s 64.5.
Where the 64.5 comes from
HVTrust dimensions vs the Multi-Agent Systems average
64.5 / 100 · 100.0% confidenceRakazo Multi-Agent Systems average (41 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 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
83.7 / 100Supply Chain Trust
Common questions about Rakazo
Does Rakazo publish package provenance?
Does Rakazo have an OpenSSF Scorecard?
Is Rakazo actively maintained?
What license does Rakazo use?
Are Rakazo'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 Rakazo'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 Rakazo?
For maintainers
HVTrust scores Rakazo 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/rakazo)
<a href="https://hvtracker.net/agents/rakazo"><img src="https://hvtracker.net/badge/rakazo.svg" alt="HVTrust"></a>
Other agents in Multi-Agent Systems
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON