Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people who keep improvising agent loops on the fly and want a more deliberate way to define goal, verification, review gates, and stop conditions before a coding agent starts changing files.
Who should use it
Who should skip it
Skip ksimback/looper if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
ksimback/looper is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-20; the source record was last checked on 2026-06-20. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. ksimback/looper leads on workflow potential (9.8) and open-source/build quality (8.4); its lowest signal is momentum (5.0), 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 ksimback/looper record combines a 8.3/10 composite score with separate popularity (52.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
Looper can hand project context to a different reviewer model or vendor CLI and can write loop artifacts into the current workspace, so test it first on a non-sensitive repo and inspect what gets shared.