Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want a serious agent orchestration layer with TypeScript ergonomics and model portability instead of stitching together brittle single-agent loops.
Who should use it
Who should skip it
Skip open-multi-agent/open-multi-agent if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
open-multi-agent/open-multi-agent is tracked by RepoRadar as a framework in the Agent Frameworks section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. The standout signals for open-multi-agent/open-multi-agent are workflow potential (10.0) and open-source/build quality (8.4), while setup ease (4.2) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The open-multi-agent/open-multi-agent record combines a 8.7/10 composite score with separate popularity (68.0), risk (conditional), and setup (advanced) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Agent orchestration frameworks only stay safe when you control what tools and accounts child agents can touch, so start with a least-privilege toolset and a staging environment.