Roo Code (archived)
Former open-source coding-agent extension. Project announced shutdown; repository archived, so this is a historical profile.
Score calculation
(8) ÷ 1 = 8.0
1 of six dimensions rated. Unrated dimensions and BDS status are excluded.
Full scoring method ↗Setup details
Privacy and telemetry evidence is historical and does not describe a currently maintained service.
Historical profile: Roo Code announced its shutdown on May 15, 2025, and its source repository is archived. Privacy notes describe the former extension and may not represent any current service.
Energy
↑Roo Code (archived) can route inference to a local model; that gives the user control over the serving machine, not a verified reduction in energy or water.
Reasoning & sources
Roo Code’s former extension supported Ollama and LM Studio, so a maintained fork could run inference on local hardware. That can make electricity observable at the device, but does not prove the local route is more efficient than cloud inference. Since the project is archived, first verify the model server and fork still work, then measure energy per completed task.
No per-task electricity, water, or emissions data, serving-region breakdown, or lifecycle assessment was found for the harness.
Training rights
↑Roo Code (archived) is a harness that connects to models; its sources do not establish a complete rights record for the training data of every model it can use.
Reasoning & sources
Roo Code’s archived extension supported local models and many remote providers. The local path offers more control over the selected model, but the archived privacy notice does not establish any model’s training permissions. If maintaining a fork, select a model with published data provenance and do not rely on the old provider list as a rights review.
The provider and exact model vary by configuration; no complete rights ledger can be inferred from the harness license or provider list.
Privacy
↑Roo Code’s historical privacy disclosure describes provider routing and telemetry, but the extension is archived.
Reasoning & sources
Roo Code supported local models, which could keep inference on the user’s machine, but the archived extension has no current maintenance assurance. Treat its privacy and security notes as historical and avoid assuming the former controls still receive fixes.
Plan, selected model/provider, enabled features, and deployment mode can change this assessment.
Openness
↑Archived extension code is Apache-2.0, but the project is no longer actively maintained.
Reasoning & sources
Roo Code’s archived repository is Apache-2.0 and remains available to inspect or fork. Its archive status means users must arrange ongoing fixes themselves. The code license does not determine the openness or terms of any connected model.
This score covers the harness/editor source only; hosted services, models, data, or enterprise features may remain proprietary.
Worker treatment
↑Roo Code’s archived repository exposes its former contribution trail, but public activity does not establish compensation or current maintainer support.
Reasoning & sources
Roo Code’s archived repository preserves the former project’s contribution history, but does not show contributor compensation or current maintainer support. The archive makes past work inspectable while leaving labor conditions unknown. If you rely on a fork, budget for maintenance and ask its maintainers about their support model.
Current worker pay, working conditions, subcontracting, safety provisions, and grievance outcomes are not established for this product’s full service chain.
Government & military
↑No harness-specific defense deployment was established in the sources reviewed; provider and parent-company records need separate attribution.
Reasoning & sources
Roo Code’s archived project materials do not identify a defense deployment. Its former provider choice means any government relationship would depend on which external model and host a user selected. Treat this as configuration-dependent, and verify the fork, provider, and host before use.
No public evidence in the reviewed material names this harness in a defense workload; absence in this review does not establish absence of indirect use.
BDS status
↑We did not find Roo Code Inc. among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.
Reasoning & sources
Roo Code Inc. is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Check the model and host this tool connects to as well as the company providing the tool.
This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.