Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI agent developers, automation builders, AI-curious readers, founders, and any developer wiring an AI coding agent to durable, signed, content-addressed file transfer between agents or to people -- and who can pair shehryarsaroya/agenttransfer with a Go 1.25+ toolchain (or the published Docker image), an outbound relay key (Resend free tier or any SMTP/SMTPS relay), a domain + ports 25
Who should use it
Who should skip it
Move on from shehryarsaroya/agenttransfer if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
shehryarsaroya/agenttransfer is tracked by RepoRadar as a open-source file-transfer protoc in the Agent-to-Agent File Transfer Protocol section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. shehryarsaroya/agenttransfer leads on workflow potential (9.9) and novelty (9.0); its lowest signal is setup ease (6.4), 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 shehryarsaroya/agenttransfer 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 'low' 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
The 28* / 3-fork repo is brand new (one week old) and at active maintenance but the security model is well-thought-out -- the consumer SHOULD review the recipient circle per agent (default 3 unique remote recipients; owner exempt; operator widens per agent) and the verified human owner required for outbound with `OPEN_SIGNUP=true`; the open-signup model is opt-in and admin-gated by default but the consumer SHOULD decide on the open-signup posture (`OPEN_SIGNUP=true` or admin-gated) and review the per-agent storage quota (20GB verified.