Roo-Code

RooCodeInc/Roo-Code

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

Ship status

Gone silent
Last push
May 15, 2026
149 days ago
Stars, last 7 weeks
Stars, weekly: 24,298 → 24,287 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

GitHub reports this repository as archived. That forces the status to silent whatever the last push says.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
24.3K
Forks
3.4K
Open issues
1K
Watchers
149
Primary language
TypeScript
Created
Oct 31, 2024
Owner
RooCodeInc · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 213 startups in the directory ship primarily in TypeScript.

Topics

This repository has no GitHub topics.

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 22%, hosted offering 49%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.97. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2026-05-15This is the badge for RooCodeInc/Roo-Code, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/RooCodeInc/Roo-Code.svg)](https://ossean.com/RooCodeInc/Roo-Code)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.