Score8.4
Popularity1.0
Risklow
TierGold
Score breakdown
Usefulness9.0
Novelty7.0
Momentum8.0
Maturity6.6
Open-source/build8.4
Evidence7.2
Workflow potential9.9
Setup ease8.8
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Go developers, AI agent developers, service-framework users, MCP server users, A2A agent users, x402 paid-tools users, AI-curious readers tracking the Go agent harness space, engineering teams wiring AI agents to their Go services, and any developer wiring a Go agent harness + service framework + MCP/A2A + x402 paid tools + durable flows to their Go workflow -- and who can pair micro/go
Who should use it
Go developers, AI agent developers, service-framework users, MCP server users, A2A agent users, x402 paid-tools users, AI-curious readers tracking the Go agent harness space, engineering teams wiring AI agents to their Go services, and any developer wiring a Go agent harness + service framework + MCP/A2A + x402 paid tools + durable flows to their Go workflow -- and who can pair micro/go-micro with the `curl -fsSL https://go-micro.dev/install.sh | sh` install for the binary surface (no Go required), the `go install go-micro.dev/v6/cmd/micro@latest` install for the Go-surface install, the `micro new` CLI for the project-init surface, the `micro run` CLI for the run surface, the `micro agent demo` CLI for the agent-demo surface, the `micro examples` CLI for the examples surface, the `micro zero-to-hero` CLI for the zero-to-hero surface, the `micro` CLI for the chat/inspect surface, the `Makefile` `make install-smoke` for the smoke-harness surface, the `Makefile` `make harness` for the full-local-contract surface, the `examples/first-agent/` directory for the smallest-first-agent surface, the `examples/support/` directory for the 0-to-hero support surface, the `internal/website/docs/guides/no-secret-first-agent.md` for the no-secret-first-agent-transcript surface, the `internal/website/docs/guides/zero-to-hero.md` for the zero-to-hero surface, the `internal/website/docs/guides/install-troubleshooting.md` for the install-troubleshooting surface, the website https://go-micro.dev for the marketing surface, the blog https://go-micro.dev/blog/3 (Anthropic sponsor) + the blog https://go-micro.dev/blog/29 (OpenAI sponsor) + the blog https://go-micro.dev/blog/8 (AtlasCloud sponsor) for the sponsor surface, the Discord https://discord.gg/G8Gk5j3uXr for the chat surface, the Go package https://pkg.go.dev/go-micro.dev/v6?tab=doc for the GoDoc surface, the SUPPORT.md for the commercial-support surface, and a target agent (service-backed, mock-model, no provider key) for the eval surfaceGo developers + AI agent developers that want the Go agent harness surface (build an agent and it gets a model, memory, tools, planning, delegation, guardrails, and service discovery) -- the right all-in-one primitive for any Go developer who has been wiring a custom per-feature Go agent harnessGo developers + MCP/A2A users that want the MCP and A2A protocols (the agent is reachable over MCP and A2A) -- the right interop primitive for any Go developer who has been writing a custom MCP/A2A adapterGo developers + paid-tools users that want the x402 paid tools (integrate paid tools via the x402 protocol) -- the right paid-tools primitive for any Go developer who has been writing a custom paid-tool integrationGo developers + service-framework users that want the durable flows (orchestrate the deterministic parts with durable flows) -- the right durable-orchestration primitive for any Go developer who has been writing a custom durable flow engineGo developers + engineering teams that want the 4 install surfaces (binary + Go + make install-smoke + make harness) + the CLI `micro` + the `micro new` + `micro run` + `micro agent demo` + `micro examples` + `micro zero-to-hero` + the 4-field corroboration (forks 2410, size 36450KB, subscribers 486, pushed 2026-07-08) + Apache-2.0 + the SUPPORT.md commercial-support surface -- the right install-friction + transparency primitive for any Go developer who has been locked to a single install path
Who should skip it
Move on from micro/go-micro if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
micro/go-micro is tracked by RepoRadar as a apache-2.0 (raw master/license c in the Go Micro v6: Go Agent Harness and Service Framew section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, micro/go-micro is strongest on workflow potential (9.9) and practical usefulness (9.0) and weakest on maturity (6.6) — a profile worth weighing against your own priorities. 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 micro/go-micro 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.
Risk explanation
The 22950* / 2410-fork / 486-subscriber / 36450KB repo is at active maintenance (pushed 2026-07-08) but the project is a service framework (NOT a finished product) -- the consumer SHOULD expect to write Go code to build their agent; the consumer SHOULD pin the Go Micro version and review the changelog; the consumer SHOULD benchmark the agent harness on the consumer's specific agent workflow before adopting; the consumer SHOULD note the project started at `micro/go-micro` in 2015 and has been through major version bumps (v3.
Evidence links
Closest alternatives / related signals
open-sourceapache-2-0go-micromicroasim-aslamgo-agent-harnessservice-frameworkmcp
