Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that already trust coding agents enough to orchestrate them, but need better routing, auditability, and workflow boundaries before those agents start touching real repositories and longer-running tasks.
Who should use it
Who should skip it
Pass on dmae97/open-multi-agent-kit if its scope or audience does not match what your team is building right now.
About this signal
dmae97/open-multi-agent-kit is tracked by RepoRadar as a developer tool in the Agent Orchestration section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, dmae97/open-multi-agent-kit is strongest on workflow potential (9.9) and practical usefulness (9.0) and weakest on setup ease (6.4) — 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 dmae97/open-multi-agent-kit a composite score of 8.4 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 'conditional' 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It is designed to coordinate coding agents that can write files and change repositories, so first evaluation should stay inside disposable repos with approval gates enabled; Autopilot profiles, browser-use integrations, and provider credentials still need separate sandbox and secret-scope review before production rollout.