How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed 20 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
24.2k
Forks
3.3k
Last Push
2026-05-15
20 days ago
Commits (4 wk)
17
Downloads (7d)
1,695,832
npm+vscode
HN mentions (30d)
—
Open Issues
1038
Rank Change
▼10
was #81
Analysis
HVTrust Dimensions
65.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.4 / 17
MaintenanceFreshness and commits
15.7 / 20
AdoptionStars and downloads
18.8 / 20
Activity Inputs
80.8 / 100
StarsRepository reach
26.3 / 30
FreshnessLast push recency
22.2 / 25
ActivityRecent commits
15.7 / 25
CommunityFork signal
16.4 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.4 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection4
CI-Tests-1
CII-Best-Practices0
Code-Review0
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?
Roo Code 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 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.4/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?
Maintained. Last push was 20 days ago.
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.
Are Roo Code's commits signed?
100% of the last 100 commits to Roo Code 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
