Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for security-minded builders and platform teams that want a more precise guardrail between agent plans and real credentials than generic allowlists or prompt-based approval wording.
Who should use it
Who should skip it
Hold off on Delego-Dev/delego until it graduates from watchlist status with stronger evidence.
About this signal
Delego-Dev/delego is tracked by RepoRadar as a agent auth firewall in the Security 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 moderate setup difficulty. Delego-Dev/delego leads on novelty (9.0) and open-source/build quality (8.4); its lowest signal is momentum (5.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 Delego-Dev/delego 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 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
This sits on the path between an agent and real credential-backed actions, so a first pilot should stay on a tightly scoped non-production workflow; The human approval home and audit ledger need to be wired carefully so approvals and MCP calls resolve against the same local state.