Is Roo Code safe?
Roo Code scores 51.9/100 (Grade C), ranked #226 of 328 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 →
Active listing, but review is needed
[5.1] repository is archived
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
51.9/100 · Grade C
Strongest Signal
Adoption
18.9/20
Weakest Signal
Safety / Integrity
4.9/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signalsThe repo was last pushed 57 days ago. Fresh activity helps separate stable projects from stale ones.
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 refreshed2026-07-11 04:00 UTC·Repo last pushed 57 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
24.3k
Forks
3.4k
Last Push
2026-05-15
57 days ago
Commits (4 wk)
0
Downloads (7d)
1,754,034
npm+vscode
HN mentions (30d)
—
Open Issues
550
Rank Change
▼1
was #225
Analysis
HVTrust Dimensions
51.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
4.9 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.8 / 17
MaintenanceFreshness and commits
8.2 / 20
AdoptionStars and downloads
18.9 / 20
Activity Inputs
59.9 / 100
StarsRepository reach
26.3 / 30
FreshnessLast push recency
17.1 / 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 Jul 10, 2026
Signed Commits
—
Unable to query
Binary-Artifacts10
Branch-Protection4
CI-Tests10
CII-Best-Practices0
Code-Review5
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies0
SAST10
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities0
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 57 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.
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.
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
Maintain Roo Code?
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.
