Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want agents to work where the conversation already lives instead of copying requests out of Slack and losing the approval trail, runtime policy, and shared context on every handoff.
Who should use it
Who should skip it
Pass on linxidnju/OpenTag if its scope or audience does not match what your team is building right now.
About this signal
linxidnju/OpenTag is tracked by RepoRadar as a tool / platform in the Team Automation section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for linxidnju/OpenTag are workflow potential (9.9) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. 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 linxidnju/OpenTag a composite score of 8.4 out of 10, placing it in the Gold 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 1.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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It can route Slack threads, artifacts, and prompts through local or external agent runtimes, so first evaluation should stay inside a restricted test workspace with explicit approvers; Sessions, approvals, outputs, and artifacts are stored locally for replay and audit, so review retention and workspace-root boundaries before handling sensitive channels.