Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Go teams that want typed, service-oriented agent code: start with the examples and evaluate whether ADK's model/tool/session abstractions fit your existing backend before adopting a heavier multi-agent platform.
Who should use it
Who should skip it
Skip google/adk-go if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
google/adk-go is tracked by RepoRadar as a developer tool in the Agent Frameworks section. It was first seen on 2026-06-16 and last updated on 2026-06-16. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, google/adk-go is strongest on workflow potential (9.6) and open-source/build quality (8.4) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed. 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 google/adk-go a composite score of 8.1 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 79.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
agent deployments may require cloud/model credentials; tool permissions need review before connecting production services.