Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want to evaluate the emerging always-on agent teammate workflow on infrastructure they control, but the operational footprint and early-stage status make it a careful pilot rather than an instant rollout.
Who should use it
Who should skip it
Pass on fancyboi999/open-tag if you need something non-technical and turnkey rather than a tool that requires comfort with CLI, dependencies, or system configuration.
About this signal
fancyboi999/open-tag is tracked by RepoRadar as a agent workspace in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'worth watch' with a Silver tier and hard setup difficulty. fancyboi999/open-tag leads on workflow potential (8.7) and open-source/build quality (8.4); 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 fancyboi999/open-tag 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 14.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
Agents run local CLI runtimes, edit files, and keep persistent shared workspaces, so start with non-production repos and tightly scoped runtime permissions; The self-hosted server stores conversations, tasks, and attachments on infrastructure you control, so review retention and access controls before inviting a wider team.