Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Go engineers who want idiomatic agent runtimes without Python, for teams standardizing on UTCP for tool calls across stacks, and for builders who need pluggable providers + middleware (retry, timeout, rate, token budget) without leaving the Go ecosystem.
Where this stands now
Protocol-Lattice/go-agent ranks #1 of 12 tracked Agent Frameworks & Orchestration items by composite score (8.4 against a section median of 7.6). The section currently carries 7 Silver, 5 Gold. RepoRadar has retained observations for this record since 2026-08-10 (45 days in the current window). Signal extremes versus the section: novelty at the 83th percentile.
Who should use it
Who should skip it
Move on from Protocol-Lattice/go-agent if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
Protocol-Lattice/go-agent is tracked by RepoRadar as a framework in the Agent Frameworks & Orchestration section. First seen 2026-08-10; the source record was last checked on 2026-08-10. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Protocol-Lattice/go-agent 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 public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The Protocol-Lattice/go-agent record combines a 8.4/10 composite score with separate popularity (0.2), risk (none), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
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
No inherent user-impacting risk is flagged from the captured evidence.