Roo Code
Website
Roo Code gives you a whole dev team of AI agents in your code editor.
Is Roo Code safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Roo Code
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: Roo Code scores 50.4/100 (Grade C), ranked #952 of 1371 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.9/10; 100% of recent commits are signed; last pushed 2026-05-15. Every point is earned from checkable signals — never paid placement. How scoring works →
How Roo Code 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.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 65.1 B · #27 of 77
- Raise the OSSF Scorecard from 3.9 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +10.6 → 61.0 C · #34 of 77
Chain of custody
Scanners check what the code says. This traces who ships Roo Code and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/RooCodeInc/Roo-Code, Apache-2.0, last pushed 2026-05-15. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection4
- Signed Releases0
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 4CI-Tests 10CII-Best-Practices 0Code-Review 5Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies 0SAST 10Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages Not linked
- npm roo-cline No source link declared No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Roo Code.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Roo Code’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Roo Code compares in Coding Agents
- #53 Aider 51.2 +0.8
- #54 Whale 50.9 +0.5
- #55 Roo Code 50.4 this agent
- #56 Tabby 49.0 −1.4
- #57 OpenCursor 48.8 −1.6
Bars show each HVTrust score; the tick marks Roo Code’s 50.4.
Where the 50.4 comes from
HVTrust dimensions vs the Coding Agents average
50.4 / 100 · 100.0% confidenceRoo Code Coding Agents average (77 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
47.4 / 100Common questions about Roo Code
Does Roo Code publish package provenance?
Does Roo Code have an OpenSSF Scorecard?
Is Roo Code actively maintained?
What license does Roo Code use?
Are Roo Code'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 →
- browser
- code
- database
- shell
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Roo Code'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 Roo Code?
For maintainers
HVTrust scores Roo Code 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/roo-code)
<a href="https://hvtracker.net/agents/roo-code"><img src="https://hvtracker.net/badge/roo-code.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON