Portfolio concentration
83%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
4 repositories updated in the last 90 days.
Leading language
Go
Portfolio mix
Go (13), Unknown (7), JavaScript (3)
Average size
66
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
83%
of the visible star count comes from this organization's top three repositories.
66
stars per repository in this same snapshot.
Go
is the most common language here, with 4 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 55% of its visible star count.
Organization pages work best when you separate portfolio breadth from flagship concentration. In go-zero team's case, the visible top three repositories account for about 83% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Go (13), Unknown (7), JavaScript (3). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | zeromicro/zero-examples go-zero examples | Go | 1.1K |
| 2 | zeromicro/awesome-zero A curated list of awesome projects that powered by go-zero. | 339 | |
| 3 | zeromicro/zero-contrib A collection of extensions and tools for go-zero. | Go | 215 |
| 4 | zeromicro/zero-skills AI-optimized knowledge base for building applications with go-zero | 89 | |
| 5 | zeromicro/ai-context Spec-driven-development with go-zero and AI. | Python | 59 |
| 6 | zeromicro/mcp-zero Model Context Protocol (MCP) server for go-zero framework - Generate APIs, RPC services, and models with AI assistance. | Go | 47 |
| 7 | zeromicro/portal go-zero official documentation | TypeScript | 33 |
| 8 | zeromicro/x This repository is part of the go-zero project but outside the main tree. It's developed under looser compatibility requirements than the go-zero project. | Go | 32 |
| 9 | zeromicro/ddl-parser A tool to parse mysql ddl. | ANTLR | 15 |
| 10 | zeromicro/zero-api zero-api is a RESTful API description language. | 14 | |
| 11 | zeromicro/go-zero-template A golang template repo for go-zero, Do not accept pr! | Smarty | 10 |
| 12 | zeromicro/api-generator The API file generator. | JavaScript | 6 |
| 13 | zeromicro/zero-test The repo for integration test of go-zero project. | 5 | |
| 14 | zeromicro/protoc-gen-zrpc-gateway | 5 | |
| 15 | zeromicro/autodoc AI generated doc for go-zero. | JavaScript | 4 |
| 16 | zeromicro/grpc-mock A gRPC mocking tool. | Go | 4 |
| 17 | zeromicro/zero-legacy The legacy mongo/mongoc packages from go-zero. | Go | 4 |
| 18 | zeromicro/antlr forked from antlr/antlr4 and remove another useless code, in order to solve the antlr official module conflict bug | Go | 4 |
| 19 | zeromicro/goctl-restclient Generate Visual Studio Code REST Client plugin files for zero-api | Go | 3 |
| 20 | zeromicro/zero-ci go-zero continuous integration. | Go | 3 |
| 21 | zeromicro/goctl-csharp goctl csharp plugin | Go | 2 |
| 22 | zeromicro/go-zero.dev go-zero.dev | JavaScript | 1 |
| 23 | zeromicro/protobuf Go support for Google's protocol buffers | Go | 1 |
| 24 | zeromicro/goctl-uniapp goctl uniapp plugin | Go | 0 |
| 25 | zeromicro/providers Provides the abstraction of cloud services. | 0 | |
| 26 | zeromicro/homebrew-goctltap homebrew goctl tap | Ruby | 0 |
| 27 | zeromicro/go-zero-release-action Automatically publish Go binaries to Github Release Assets through Github Action. | Shell | 0 |
| 28 | zeromicro/redirect The redirect pages | HTML | 0 |
| 29 | zeromicro/faker To response a fake data for struct | 0 | |
| 30 | zeromicro/doc-contributor-generator A tool for go-zero document to generate contributors which used by github action, not accept pull request and issue. | Go | 0 |
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.