Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams trying to reduce credential sprawl across CI, SSH, cron, and background agent workflows, but it still sits on a sensitive account-access boundary that deserves a careful first rollout.
Who should use it
Who should skip it
Skip agentrhq/authsome for now if your priority is a tool you can use today without configuring a build pipeline or development environment.
About this signal
agentrhq/authsome is tracked by RepoRadar as a credential gateway in the Agents and Automation section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'worth watch' with a Silver tier and hard setup difficulty. agentrhq/authsome leads on workflow potential (8.5) and open-source/build quality (8.4); its lowest signal is momentum (4.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 agentrhq/authsome a composite score of 7.7 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 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Handles OAuth sessions and API keys for live services, so first rollout should stay on a narrow provider set with explicit credential rotation and audit review; An auth proxy sits between agents and real external systems, so provider mappings and header injection should be tested on non-production accounts before wider use.