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 inside Slack or Microsoft Teams without collapsing accountability, approvals, and tool access into one opaque shared service account.
Who should use it
Who should skip it
Pass on tomascupr/operant if its scope or audience does not match what your team is building right now.
About this signal
tomascupr/operant 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. tomascupr/operant leads on workflow potential (10.0) and practical usefulness (9.0); its lowest signal is momentum (6.0), 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 tomascupr/operant a composite score of 8.5 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 act across Slack or Teams plus connected SaaS accounts under each user's OAuth session, so first evaluation should stay inside a low-risk workspace with limited app scopes; The self-hosted stack stores policy decisions, audit logs, and session records, so review retention and access boundaries before routing sensitive internal work through it.