Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
That matters because coding agents are becoming more capable, but a lot of the trust problem now lives in planning, review, and proving the result works. A swarm plugin focused on that gap is more useful than another plain chat wrapper.
Who should use it
Who should skip it
Skip ZaxbyHub/opencode-swarm if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
ZaxbyHub/opencode-swarm is tracked by RepoRadar as a developer tool in the Radar 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 moderate setup difficulty. Across RepoRadar's eight signals, ZaxbyHub/opencode-swarm is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. 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 ZaxbyHub/opencode-swarm record combines a 8.7/10 composite score with separate popularity (74.0), risk (conditional), and setup (moderate) 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
This plugin can help orchestrate code edits and tool-driven development steps, so test it on a non-critical repository before trusting it with production code or credentials.