Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineering teams experimenting with higher-autonomy coding workflows and wanting a clearer bridge from issue queues to reproducible agent runs.
Where this stands now
the-open-engine/zeroshot ranks #175 of 2402 tracked Radar items by composite score (8.5 against a section median of 5.2). The section currently carries 1295 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-06-20 (101 days in the current window). Signal extremes versus the section: momentum at the 80th percentile; novelty at the 80th percentile.
Who should use it
Who should skip it
Pass on the-open-engine/zeroshot if your environment cannot support the access controls and sandboxing this risk profile requires.
About this signal
the-open-engine/zeroshot 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 'worth watch' with a Silver tier and advanced setup difficulty. Across RepoRadar's eight signals, the-open-engine/zeroshot is strongest on workflow potential (9.3) and open-source/build quality (8.4) and weakest on setup ease (4.2) — 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 the-open-engine/zeroshot record combines a 8.5/10 composite score with separate popularity (10.0), risk (medium), and setup (advanced) 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
It can autonomously edit code and operate against live issue backends, so keep repository isolation and human review in place.