Item detail
github.com

Zoo-Code-Org/Zoo-Code

Zoo-Code-Org/Zoo-Code is an apache-2.0 community continuatio that RepoRadar is tracking in its Zoo Code: Community Continuation of Roo Code (VS section, currently rated Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.1 out of 10.

Score8.0
Popularity1.0
Risklow
TierGold
Score breakdown
Usefulness8.0
Novelty7.0
Momentum8.0
Maturity6.3
Open-source/build8.4
Evidence7.2
Workflow potential9.1
Setup ease8.8

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for VS Code users, AI coding agent developers, AI-curious readers, engineering teams that were using Roo Code and need a community-maintained successor, and any developer wiring a multi-agent AI extension into VS Code -- and who can pair Zoo-Code-Org/Zoo-Code with VS Code for the editor surface, the VS Code Marketplace (search 'Zoo Code' or install via the marketplace URL) for the install s

Who should use it

VS Code users, AI coding agent developers, AI-curious readers, engineering teams that were using Roo Code and need a community-maintained successor, and any developer wiring a multi-agent AI extension into VS Code -- and who can pair Zoo-Code-Org/Zoo-Code with VS Code for the editor surface, the VS Code Marketplace for the install surface, the existing Roo Code feature set for the capability surface, the community Discord for the support surface, and the upstream Roo Code feature parity for the migration surfaceVS Code users + engineering teams that were using Roo Code and need a community-maintained successor -- the right handoff primitive for any VS Code user who was using Roo CodeVS Code users + engineering teams that want the full Roo Code feature set (multi-agent, code review, refactor, test generation, browser automation, custom modes) -- the right capability-coverage primitive for any VS Code user who has been using Roo Code and wants feature parityVS Code users + engineering teams that want a real TypeScript monorepo (apps/ + locales/ + .vscode/ + .github/ + .husky/ + .changeset/ + codecov.yml + knip.json + .roomodes + .roo/ + package.json + CHANGELOG.md + SECURITY.md + AGENTS.md) -- the right engineering-rigor primitive for any VS Code user who has been burned by a single-file VS Code extensionVS Code users + engineering teams that want the VS Code Marketplace package (ZooCodeOrganization.zoo-code) + community Discord + subreddit + active issue tracker -- the right install + support primitive for any VS Code user who has been burned by an abandoned extension

Who should skip it

Move on from Zoo-Code-Org/Zoo-Code if the licensing terms, language support, or platform requirements do not fit your project.

About this signal

Zoo-Code-Org/Zoo-Code is tracked by RepoRadar as a apache-2.0 community continuatio in the Zoo Code: Community Continuation of Roo Code (VS section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, Zoo-Code-Org/Zoo-Code is strongest on workflow potential (9.1) and setup ease (8.8) and weakest on maturity (6.3) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned Zoo-Code-Org/Zoo-Code a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

The 1258* / 182-fork repo is at active maintenance (pushed 2026-07-07) but this is a community continuation; not a from-scratch new project -- the consumer SHOULD evaluate the Zoo Code core team velocity and the upstream Roo Code feature parity; the consumer SHOULD pin the Zoo Code version and review the changelog; the consumer SHOULD benchmark the upstream Roo Code feature parity (verify each Roo Code feature is still available in Zoo Code) before relying on any specific feature.

Evidence links
Closest alternatives / related signals
open-sourceapache-2-0zoo-codezoo-code-orgroo-coderoo-code-successorvs-code-extensionvs-code-marketplace