Is Rakazo safe to use?

Rakazo has an HVTrust score of 64.3/100 (Grade C), ranked #343 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Rakazo?

Rakazo scores 64.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.9k GitHub stars and is categorized under Multi-Agent Systems.

Rakazo

elie222/rakazo

Open-source Grok Bot alternative. Choose your own model and sandbox.

Multi-Agent Systems TypeScript Grade C Listed Apache-2.0

64.3/100

Rank #343 of 1320

Compare Rakazo

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-04 · 0d ago

Recent change

Rank +12

Is Rakazo safe? Rakazo scores 64.3/100 (Grade C), ranked #343 of 1320 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.7/10; 100% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#5 Concordia — 65.0 (B) → #6 Multica — 64.7 (C) → #8 Open Multi-Agent — 64.3 (C) → #9 Agency Agents — 63.9 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-03

Rank Moved

Rank dropped 23 spots (#312 → #335)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-02

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.7/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.

Compare with AIPass Get email alerts for Rakazo View Multi-Agent Systems Report missing data

81.4

Activity sub-score · out of 100

In Multi-Agent Systems

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

2026-08-16 2026-09-04

Activity & Reach

Stars

1.9k

Forks

328

Last Push

2026-09-04

today

Commits (4 wk)

662

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼8

was #335

Analysis

HVTrust Dimensions vs Multi-Agent Systems

64.3 / 100 · 100.0% confidence

Rakazo Multi-Agent Systems average (36 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.1 / 25

4.1 above avg 8.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.4 above avg 11.9

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.6 above avg 12.4

AdoptionLog-scaled stars · package downloads

7.9 / 20

1.9 below avg 9.8

Activity Inputs

81.4 / 100

StarsRepository reach

19.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Sep 3, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 4

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 5

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is Rakazo safe?

Rakazo has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Rakazo publish package provenance?

No published build provenance is currently detected for Rakazo. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Rakazo have an OpenSSF Scorecard?

Rakazo has an OpenSSF Scorecard score of 5.7/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 Rakazo actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Rakazo use?

Rakazo ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Rakazo's commits signed?

100% of the last 100 commits to Rakazo 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.

Compare Rakazo head-to-head

Rakazo vs AIPass → Rakazo vs Solace Agent Mesh → Rakazo vs CAMEL →

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

high confidence

Implemented

Rakazo appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 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.

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-02

Mcp Status Changed

Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-03

Rank Moved

Rank dropped 23 spots (#312 → #335)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-02

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-02

Rank Moved

Rank rose 120 spots (#432 → #312)

2026-09-02

HVTrust Changed

HVTrust up 5.1pts (59.3 → 64.4)

2026-09-01

Rank Moved

Rank dropped 36 spots (#396 → #432)

2026-08-31

Scorecard Added

OSSF Scorecard: 6.4/10

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 754 spots (#1150 → #396)

2026-08-31

HVTrust Changed

HVTrust up 37.7pts (22.8 → 60.5)

2026-08-30

Rank Moved

Rank dropped 38 spots (#1112 → #1150)

2026-08-29

Rank Moved

Rank dropped 39 spots (#1073 → #1112)

2026-08-28

Rank Moved

Rank dropped 29 spots (#1044 → #1073)

2026-08-27

Rank Moved

Rank dropped 21 spots (#1023 → #1044)

2026-08-26

Rank Moved

Rank dropped 88 spots (#935 → #1023)

2026-08-22

Rank Moved

Rank rose 10 spots (#951 → #941)

2026-08-17

Rank Moved

Rank rose 26 spots (#987 → #961)

2026-08-16

Newly Listed

First tracked at rank #987

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/rakazo.svg)](https://hvtracker.net/agents/rakazo)
            
HTML:
            <a href="https://hvtracker.net/agents/rakazo"><img src="https://hvtracker.net/badge/rakazo.svg" alt="HVTrust"></a>

Other agents in Multi-Agent Systems

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