Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want custom agent surfaces without hand-assembling packaging, policy, memory, and release plumbing from scratch.
Who should use it
Who should skip it
Consider ruvnet/metaharness lower priority if you already have a working solution in this category.
About this signal
ruvnet/metaharness is tracked by RepoRadar as a agent harness builder in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for ruvnet/metaharness are workflow potential (9.9) and novelty (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. 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 ruvnet/metaharness 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 5.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
Generated harnesses can execute tools and ship their own policies, so inspect the scaffolded permissions and memory settings before publishing or sharing them; Darwin Mode can mutate harness configuration behind evaluation gates, so keep first runs in a test repo until you review what the evolution loop is allowed to change.