Roo Code
Tracked across 28 snapshots (2026-02-02 → 2026-06-12).
Latest rating
37
Rating delta
-37
Latest signal
Detected
Detected
Caps now applied
3
Rating timeline
Dimension trajectory
Autonomy
7/20Integration
7/20Context
11/20Compliance
5/20Viability
4/20Interface
10/20Cap timeline
Notable events
- 2026-02-06SignalAssessed → Detected
- 2026-02-06Cap +funding-concerns
- 2026-02-26SignalDetected → Tracked
- 2026-02-26Cap −funding-concerns
- 2026-05-04Drop-9 rating
- 2026-05-05Jump+13 rating
- 2026-05-16SignalTracked → Detected
- 2026-05-16Cap +stalled-development
- 2026-05-16Cap +community-exodus
- 2026-05-16Drop-39 rating
- 2026-05-28Cap +critical-security-vuln
What would move this next
Status is terminal. No upgrade path for this entry — the product is archived and now carries an unpatchable critical RCE. Monitor only: if Roomote (the replacement product from the same team) reaches GA and gains adoption signals, create a NEW Roomote tool entry rather than reviving roo-code. If a community fork (Zoo Code, Kilo Code) achieves independent significance, evaluate it as its own entry — do not retro-promote roo-code based on fork activity. Do not lift the critical-security-vuln cap: CVE-2026-30307 cannot be patched in an archived repo.