zeromicro/go-zero

Prefer this fork if you are building Simple Admin-specific tooling and want a go-zero base that has already been reshaped around those workflows. Prefer upstream if you want broad community compatibility, stock examples, and the least surprising go-zero behavior.

Choose this fork if you want go-zero plus extra storage-layer and workflow customization and you can absorb ongoing upstream sync work. Choose upstream if you want the newest goctl, Redis, and REST fixes with less maintenance risk.

Choose upstream unless you specifically need this fork’s legacy customizations; the fork is stale, heavily diverged, and likely misses a large amount of recent upstream capability and maintenance.

Choose this fork only if the MCP and packaging/customization work is the point. If you mainly want standard go-zero, upstream is the safer choice because this fork is significantly divergent and lags recent framework fixes and upgrades.

Prefer this fork only if you need its added MCP/goctl/file-serving work and can accept an older, divergent codebase. For most adopters wanting the latest stable go-zero, upstream is the safer choice.

Choose this fork only if its extra metrics, timeout, and injection behavior are directly valuable and you are prepared to maintain a large upstream gap. For most adopters, upstream go-zero is the safer default because it is far more current and actively maintained.

Choose this fork only if you need its specific older customizations. For new adoption, upstream is the better default because this fork is stale, materially behind, and likely to cost more to maintain than it saves.

Choose this fork only if you need its specific customizations and are prepared to own the maintenance burden. For most new adopters, upstream go-zero is the safer choice because this fork is years behind and materially diverged.