Organizations show portfolio shape
Use this route as a portfolio map, not a simple total-star leaderboard. The first fold should tell you who leads overall, who has the widest footprint, and whether visibility is concentrated in one flagship or spread across a broader stack.
Top publisher
Microsoft
623K stars
Best read as long-term portfolio visibility.
Widest footprint
Microsoft
10 repos
Breadth matters when you want many maintained entry points in one publisher.
Highest concentration
LangChain
96%
Shows who is most dependent on one breakout repository.
Balanced portfolio
43%
Lower top-three concentration means attention is spread across multiple repositories.
Portfolio read
Flagship-Driven
Use this pattern to spot organizations whose visibility is anchored by a single project.
96%
Portfolio read
Broad Portfolios
Breadth matters when you want publishers with many maintained entry points across a stack.
10
Portfolio read
Balanced Portfolios
Lower concentration signals that attention is spread across several repositories instead of one flagship.
43%
Full ranking
30 organizations tracked·0 from snapshot, 30 from fallback
0 from snapshot, 30 from fallback30 organizations
| # | Organization | Profile | Repos | Stars | Share |
|---|---|---|---|---|---|
| 1 | Top: vscode, PowerToys, TypeScript | Distributed | 10 | 623K | |
| 2 | Top: react, react-native, docusaurus | Distributed | 10 | 535K | |
| 3 | Top: material-design-icons, guava, zx | Distributed | 10 | 320K | |
| 4 | Top: tensorflow, models, tfjs | Top-heavy | 3 | 274K | |
| 5 | Top: vue, core, router | Flagship-driven | 3 | 252K | |
| 6 | Top: next.js, swr, turbo | Top-heavy | 3 | 171K | |
| 7 | Top: transformers, diffusers, datasets | Flagship-driven | 3 | 160K | |
| 8 | Top: kubernetes, minikube, kops | Flagship-driven | 3 | 148K | |
| 9 | Top: angular, angular-cli, components | Top-heavy | 3 | 143K | |
| 10 | Top: go, tools, lint | Flagship-driven | 3 | 128K | |
| 11 | Top: tailwindcss, headlessui, heroicons | Top-heavy | 3 | 119K | |
| 12 | Top: rust, book, cargo | Flagship-driven | 3 | 117K | |
| 13 | Top: whisper, gym, chatgpt-retrieval-plugin | Top-heavy | 3 | 108K | |
| 14 | Top: node, undici, corepack | Flagship-driven | 3 | 106K | |
| 15 | Top: grafana, k6, loki | Top-heavy | 3 | 105K | |
| 16 | Top: elasticsearch, kibana, logstash | Top-heavy | 3 | 100K | |
| 17 | Top: spark, airflow, kafka | Top-heavy | 3 | 99K | |
| 18 | Top: nest, typeorm, swagger | Top-heavy | 3 | 97K | |
| 19 | Top: terraform, vault, consul | Top-heavy | 3 | 96K | |
| 20 | Top: pytorch, vision, audio | Flagship-driven | 3 | 92K | |
| 21 | Top: flask, click, jinja | Flagship-driven | 3 | 90.8K | |
| 22 | Top: django, channels, asgiref | Flagship-driven | 3 | 82K | |
| 23 | Top: langchain, langgraph, langsmith-sdk | Flagship-driven | 3 | 78.5K | |
| 24 | Top: cpython, mypy, peps | Flagship-driven | 3 | 78K | |
| 25 | Top: supabase, realtime, postgrest-js | Flagship-driven | 3 | 61.8K | |
| 26 | Top: prisma, studio, docs | Flagship-driven | 3 | 40.5K | |
| 27 | Top: compose, cli, docs | Flagship-driven | 3 | 40K | |
| 28 | Top: aws-cli, aws-cdk, chalice | Top-heavy | 3 | 35K | |
| 29 | Top: quiche, cloudflared, workers-sdk | Top-heavy | 3 | 18K | |
| 30 | Top: stripe-node, stripe-python, react-stripe-js | Top-heavy | 3 | 5.5K |
Next step after the portfolio scan
Open a single organization for concentration detail, move into repository compare mode, or step back to the broader GitHub anchor map.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
What to verify after the leaderboard
Total stars are best treated as a discovery signal, not a verdict on engineering quality. Once an organization looks interesting, the next useful checks are release cadence, maintainer activity, flagship dependency concentration, and whether the portfolio reflects one hit project or a broader product surface.
For more background on how GitStar handles source data and editorial interpretation, see Methodology & Editorial Standards.