Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that actually want agents to operate over email on their own domains, with mailbox isolation, provenance, and reviewable send paths instead of bolting ad hoc IMAP and SMTP credentials into a generic agent.
Who should use it
Who should skip it
Move on from agentteamhq/agentteam-email if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
agentteamhq/agentteam-email is tracked by RepoRadar as a email infrastructure in the AI Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. The standout signals for agentteamhq/agentteam-email are workflow potential (9.3) and open-source/build quality (8.4), while setup ease (4.2) 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 agentteamhq/agentteam-email a composite score of 8.2 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It gives agents real inboxes and outbound mail paths, so first evaluation should stay on domains and mailboxes you control with human draft review enabled for any customer-facing send; The stack handles credentials, sessions, archives, and message evidence, so read SECURITY.md and rotate test secrets before opening it to production traffic.