Roo Code vs Cline: Which Is More Actively Maintained? Live GitHub Data
Roo Code began as a fork of Cline, and both are open-source coding agents for VS Code that can edit files and run commands with your approval. This page compares how actively each project is maintained, using live data from GitHub.
GitHub data checked 5 minutes ago.
Side by side
| Measure | Roo Code | Cline |
|---|---|---|
| Status | Archived | Active |
| Commits, last 91 days | 0 | 1,057 |
| Same 91 days a year earlier | 700 | 917 |
| Change vs last year | −100% | +15% |
| Last commit | 15 May 2026 | 18 Oct 2026 |
| GitHub stars | 24,272 | 70,514 |
| Stars gained, daily snapshots | -1 in 1 day | +102 in 2 days |
| Licence | Apache-2.0 | Apache-2.0 |
| Managed cloud | Not checked | Not checked |
| Visitor rating | —0 of 3 ratings needed | —1 of 3 ratings needed |
What the numbers say
In the last 91 days, Roo Code’s default branch received 0 commits and Cline’s received 1,057. Against the same 91 days a year earlier, Roo Code is at −100% and Cline at +15%. The index labels Roo Code “archived” and Cline “active”. Roo Code has 24,272 GitHub stars and Cline has 70,514; stars show how many people bookmarked a project, not how many use it.
What this comparison does not tell you
These are maintenance signals only. They do not measure speed, output quality, features, documentation or how easy either tool is to run, and we have not benchmarked either tool for this page. A quiet repository can still be a good fit for a stable job, and a busy one can still break between releases. Use the numbers to decide what to check next, not which tool is better.
Each tool’s full record
Related comparisons
How this is measured: commits on each repository’s default branch counted through the GitHub API, the last 91 days against the same 91 days a year earlier; stars, licence and archived flag from the repository; README checked daily for maintenance notices. Visitor ratings come from visitors to each tool’s page, not from EvalAITools.