Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for advanced builders who want one reusable operating layer for multiple coding-agent harnesses instead of rebuilding guardrails, memory, and repo rules for each tool from scratch.
Where this stands now
affaan-m/ECC ranks #34 of 2195 tracked Radar items by composite score (8.7 against a section median of 6.2). The section currently carries 1090 Bronze, 646 Gold, 459 Silver. RepoRadar has retained observations for this record since 2026-06-20 (97 days in the current window). Signal extremes versus the section: momentum at the 89th percentile.
Who should use it
Who should skip it
Skip affaan-m/ECC unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
affaan-m/ECC is tracked by RepoRadar as an agent project in the Radar section. First seen 2026-06-20; the source record was last checked on 2026-06-20. The current verdict is 'watch' with a Gold tier and moderate setup difficulty. affaan-m/ECC leads on workflow potential (9.5) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. 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 affaan-m/ECC record combines a 8.7/10 composite score with separate popularity (30.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
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 captures and shapes live agent behavior across repositories and toolchains, so teams should review what data, prompts, hooks, and credentials the workflow layer can touch.