Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for advanced builders who want to study or sandbox a real multi-agent operating model with persistent tasks, agent hierarchy, and browser-based work rather than another demo orchestration layer.
Who should use it
Who should skip it
Pass on sandydasari/openacme if your environment cannot support the access controls and sandboxing this risk profile requires.
About this signal
sandydasari/openacme is tracked by RepoRadar as a agent system in the AI Infrastructure section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'worth watch' with a Silver tier and hard setup difficulty. sandydasari/openacme leads on open-source/build quality (8.4) and workflow potential (8.3); its lowest signal is setup ease (4.2), so factor that in before investing setup time. 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 sandydasari/openacme a composite score of 7.9 out of 10, placing it in the Silver 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 81.0 and never affects the composite score or tier. The risk label of 'high' 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
The daemon stores sessions, tasks, agent memories, OAuth tokens, and browser state under ~/.openacme, so a compromise exposes a full operating context; Agents inherit logged-in browser sessions and can browse or publish on your behalf, so start with throwaway accounts and a tightly scoped evaluation workspace; Recurring autonomous tasks can trigger external actions while you are away, so require a human gate for anything that posts, spends money, or touches production systems.