Organizations

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

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

Google

43%

Lower top-three concentration means attention is spread across multiple repositories.

Open Top 100 Compare repositories

Portfolio read

Flagship-Driven

Use this pattern to spot organizations whose visibility is anchored by a single project.

96%from one breakout repo

Portfolio read

Broad Portfolios

Breadth matters when you want publishers with many maintained entry points across a stack.

10repos in the broadest footprint

Microsoft

10 repos tracked

Open

Balanced Portfolios

Lower concentration signals that attention is spread across several repositories instead of one flagship.

43%held by the top three repos

Google

Top 3 account for 43%

Open

Microsoft

Top 3 account for 58%

Open

Full ranking

30 organizations tracked·0 from snapshot, 30 from fallback

0 from snapshot, 30 from fallback30 organizations

#	Organization	Profile	Repos	⭐ Stars
1	Microsoft@microsoft Top: vscode, PowerToys, TypeScript	Distributed	10	623K
2	Meta@facebook Top: react, react-native, docusaurus	Distributed	10	535K
3	Google@google Top: material-design-icons, guava, zx	Distributed	10	320K
4	TensorFlow@tensorflow Top: tensorflow, models, tfjs	Top-heavy	3	274K
5	Vue.js@vuejs Top: vue, core, router	Flagship-driven	3	252K
6	Vercel@vercel Top: next.js, swr, turbo	Top-heavy	3	171K
7	Hugging Face@huggingface Top: transformers, diffusers, datasets	Flagship-driven	3	160K
8	Kubernetes@kubernetes Top: kubernetes, minikube, kops	Flagship-driven	3	148K
9	Angular@angular Top: angular, angular-cli, components	Top-heavy	3	143K
10	Go@golang Top: go, tools, lint	Flagship-driven	3	128K
11	Tailwind Labs@tailwindlabs Top: tailwindcss, headlessui, heroicons	Top-heavy	3	119K
12	Rust@rust-lang Top: rust, book, cargo	Flagship-driven	3	117K
13	OpenAI@openai Top: whisper, gym, chatgpt-retrieval-plugin	Top-heavy	3	108K
14	Node.js@nodejs Top: node, undici, corepack	Flagship-driven	3	106K
15	Grafana Labs@grafana Top: grafana, k6, loki	Top-heavy	3	105K
16	Elastic@elastic Top: elasticsearch, kibana, logstash	Top-heavy	3	100K
17	Apache Software Foundation@apache Top: spark, airflow, kafka	Top-heavy	3	99K
18	NestJS@nestjs Top: nest, typeorm, swagger	Top-heavy	3	97K
19	HashiCorp@hashicorp Top: terraform, vault, consul	Top-heavy	3	96K
20	PyTorch@pytorch Top: pytorch, vision, audio	Flagship-driven	3	92K
21	Pallets@pallets Top: flask, click, jinja	Flagship-driven	3	90.8K
22	Django@django Top: django, channels, asgiref	Flagship-driven	3	82K
23	LangChain@langchain-ai Top: langchain, langgraph, langsmith-sdk	Flagship-driven	3	78.5K
24	Python@python Top: cpython, mypy, peps	Flagship-driven	3	78K
25	Supabase@supabase Top: supabase, realtime, postgrest-js	Flagship-driven	3	61.8K
26	Prisma@prisma Top: prisma, studio, docs	Flagship-driven	3	40.5K
27	Docker@docker Top: compose, cli, docs	Flagship-driven	3	40K
28	Amazon Web Services@aws Top: aws-cli, aws-cdk, chalice	Top-heavy	3	35K
29	Cloudflare@cloudflare Top: quiche, cloudflared, workers-sdk	Top-heavy	3	18K
30	Stripe@stripe 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.

Open a top organization Compare repositories Open Top 100

Learn and methodology

Keep trust-building context reachable, but behind the first data read instead of ahead of it.

Guide Methodology Articles Weekly Digest

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.