Is Roo Code safe to use?

Roo Code has an HVTrust score of 49.1/100 (Grade D), ranked #454 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Roo Code?

Roo Code scores 49.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 24.3k GitHub stars and is categorized under Coding Agents.

Roo Code

RooCodeInc/Roo-Code

Roo Code gives you a whole dev team of AI agents in your code editor.

Coding Agents TypeScript Grade D Listed Apache-2.0

49.1/100

Rank #454 of 1283

Compare Roo Code

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-05-15 · 92d ago

Recent change

Cleared +8

Is Roo Code safe? Roo Code scores 49.1/100 (Grade D), ranked #454 of 1283 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; recent commits are unsigned; last pushed 2026-05-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#39 HumanLayer — 49.6 (D) → #40 Grok CLI — 49.5 (D) → #42 opencode — 46.6 (D) → #43 Stakpak Agent — 45.5 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-15

Warning Cleared

Warning cleared: eligibility issues resolved

2026-08-15

Rank Moved

Rank rose 11 spots (#465 → #454)

2026-08-13

Activity Went Stale

No commits for 90 days

Maintainer Checklist

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 92 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Roo Code View Coding Agents Report missing data

55.1

Activity sub-score · out of 100

#41

In Coding Agents

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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

2026-08-11 2026-08-15

Activity & Reach

Stars

24.3k

Forks

3.4k

Last Push

2026-05-15

92 days ago

Commits (4 wk)

Downloads (7d)

1,754,034

npm+vscode

HN mentions (30d)

—

Open Issues

550

Rank Change

▲11

was #465

Analysis

HVTrust Dimensions vs Coding Agents

49.1 / 100 · 100.0% confidence

Roo Code Coding Agents average (67 agents)

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

4.9 / 25

2.8 below avg 7.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

11.8 / 17

0.6 above avg 11.2

Maintenance60% last-push freshness · 40% commit activity

5.9 / 20

9.3 below avg 15.2

AdoptionLog-scaled stars · package downloads

18.9 / 20

6.8 above avg 12.1

Activity Inputs

55.1 / 100

StarsRepository reach

26.3 / 30

FreshnessLast push recency

12.2 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

16.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Aug 15, 2026

Signed Commits

—

Unable to query

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Roo Code safe?

Public trust evidence for Roo Code 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 Roo Code publish package provenance?

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

Does Roo Code have an OpenSSF Scorecard?

Roo Code has an OpenSSF Scorecard score of 3.9/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 Roo Code actively maintained?

Slowing down. Last push was 92 days ago — keep an eye on whether activity resumes.

What license does Roo Code use?

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

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

high confidence

Implemented

Roo Code appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

7 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Marketplace

Marketplace plugin/integration surface detected.

browser
code
database
shell

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

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

2026-08-13

Activity Went Stale

No commits for 90 days

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-15

Warning Cleared

Warning cleared: eligibility issues resolved

2026-08-15

Rank Moved

Rank rose 11 spots (#465 → #454)

2026-08-13

Activity Went Stale

No commits for 90 days

2026-08-13

Rank Moved

Rank dropped 14 spots (#452 → #466)

2026-08-12

Rank Moved

Rank rose 12 spots (#464 → #452)

2026-08-10

Warning Issued

Warning: eligibility issues detected

2026-08-10

Rank Moved

Rank dropped 18 spots (#446 → #464)

2026-08-09

Warning Cleared

Warning cleared: eligibility issues resolved

2026-08-08

Rank Moved

Rank dropped 111 spots (#331 → #442)

2026-07-15

Warning Issued

Warning: eligibility issues detected

2026-07-15

Rank Moved

Rank dropped 21 spots (#270 → #291)

2026-07-14

Warning Cleared

Warning cleared: eligibility issues resolved

2026-07-14

Rank Moved

Rank dropped 16 spots (#254 → #270)

2026-07-13

Warning Issued

Warning: eligibility issues detected

2026-07-13

Rank Moved

Rank dropped 28 spots (#226 → #254)

2026-07-12

Warning Cleared

Warning cleared: eligibility issues resolved

2026-06-24

Rank Moved

Rank dropped 25 spots (#186 → #211)

2026-06-23

Warning Issued

Warning: eligibility issues detected

2026-06-23

Rank Moved

Rank dropped 11 spots (#175 → #186)

2026-06-20

Rank Moved

Rank dropped 15 spots (#144 → #159)

2026-06-20

HVTrust Changed

HVTrust down 5.1pts (59.9 → 54.8)

2026-06-18

Scorecard Added

OSSF Scorecard: 3.4/10

2026-06-18

Grade Changed

Trust grade D → C

2026-06-18

Rank Moved

Rank rose 63 spots (#203 → #140)

2026-06-18

HVTrust Changed

HVTrust up 24.6pts (35.3 → 59.9)

2026-06-16

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-16

Grade Changed

Trust grade B → D

2026-06-16

Rank Moved

Rank dropped 98 spots (#103 → #201)

2026-06-16

HVTrust Changed

HVTrust down 29.8pts (65.1 → 35.3)

2026-06-16

Activity Score Changed

Activity score down 17pts (80 → 63)

2026-06-15

Scorecard Added

OSSF Scorecard: 3.4/10

2026-06-15

Grade Changed

Trust grade D → B

2026-06-15

Rank Moved

Rank rose 97 spots (#200 → #103)

2026-06-15

HVTrust Changed

HVTrust up 29.7pts (35.4 → 65.1)

2026-06-15

Activity Score Changed

Activity score up 17pts (64 → 80)

2026-06-13

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-13

Grade Changed

Trust grade B → D

2026-06-13

Rank Moved

Rank dropped 98 spots (#103 → #201)

2026-06-13

HVTrust Changed

HVTrust down 29.8pts (65.3 → 35.5)

2026-06-13

Activity Score Changed

Activity score down 17pts (80 → 64)

2026-06-11

Scorecard Added

OSSF Scorecard: 3.4/10

2026-06-11

Warning Cleared

Warning cleared: eligibility issues resolved

2026-06-11

Grade Changed

Trust grade D → B

2026-06-11

Rank Moved

Rank rose 97 spots (#200 → #103)

2026-06-11

HVTrust Changed

HVTrust up 29.8pts (35.6 → 65.4)

2026-06-11

Activity Score Changed

Activity score up 16pts (64 → 80)

2026-06-10

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-10

Warning Issued

Warning: eligibility issues detected

2026-06-10

Grade Changed

Trust grade B → D

2026-06-10

Rank Moved

Rank dropped 103 spots (#97 → #200)

2026-06-10

HVTrust Changed

HVTrust down 29.9pts (65.5 → 35.6)

2026-06-10

Activity Score Changed

Activity score down 16pts (80 → 64)

2026-06-09

Newly Listed

First tracked at rank #97

GitHub → npm: roo-cline

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/roo-code.svg)](https://hvtracker.net/agents/roo-code)
            
HTML:
            <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

Data sources
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.3 · Raw JSON