GitHub Organization Analyzer
Analyze any GitHub organization to estimate team size, activity levels, and engineering health. See contributor counts, active repos, tech stack, and more.
Type in any public GitHub organization and this tool reads back a quick picture of its engineering team. It pulls org metadata, the most recently active repositories, and the people contributing to them, then turns that into an estimated team size, an activity read, the tech stack in use, and a single health score.
Everything here comes from data GitHub already makes public. There is no login, no scraping, and no private access. That is also the limit: what you see reflects public repositories only, so an org that does most of its work in private will look quieter than it really is.
Use it to size up a potential employer, scope a competitor, vet an open-source dependency, or just satisfy your curiosity about how a company actually ships.
Enter a GitHub organization name above to analyze their engineering metrics.
Try popular orgs like , , or
Limitations
- Only analyzes public repositories and contributors
- Team size is a lower bound (private repos, non-coders not counted)
- Rate limited to 60 requests/hour without authentication
- Cannot measure code quality, review speed, or deployment frequency
How it’s calculated
The tool runs a short sequence of calls against the public GitHub REST API. No token is sent, so it shares the unauthenticated budget of 60 requests per hour per IP. Every response updates the rate-limit counter you see under the search box.
What it fetches
- Org metadata from /orgs/{name}: name, description, location, website, avatar, and public repo count.
- Up to 30 source repositories sorted by most recent push, so the freshest work surfaces first.
- Contributor lists for the top 5 of those repos, capped to keep the analysis inside the rate limit.
How the signals are built
- Estimated team size is the count of unique human contributors across those top repos. Accounts ending in [bot] are dropped.
- Active repos (30d) counts how many of the fetched repos were pushed to in the last 30 days. Ten or more reads as high, three or more as medium, below that as low.
- Tech stack aggregates the primary language declared on each repo, ranked by how many repos use it.
- Community totals sum stars and forks across the fetched repos.
The health score
The 0-100 health score is a weighted composite, not a quality grade. Team size contributes up to 30 points and rewards the 50-500 contributor band most. Recent activity adds up to 25, language diversity up to 15, stars and forks up to 20, and a complete org profile (a description and a website link) up to 10. It is a rough proxy for engineering investment and visibility, and it says nothing about code quality, review speed, or how often the team deploys.
Worked example
Say you analyze a mid-sized SaaS company. The tool finds 30 source repos, 12 of them pushed within the last 30 days, and 64 unique human contributors across the top 5 active repos.
- Team size 64 lands in the 50-500 band, so it earns the full 30 points and reads as a Large Team.
- 12 active repos clears the threshold of 10, so activity scores 25 points and shows as High Activity.
- Six distinct languages give the full 15 points for diversity, with TypeScript ranked first as the primary stack.
- Around 4,000 stars across the fetched repos adds 20 points, and a filled-in description plus website link adds 10.
That sums to roughly 90 out of 100 - a team that is large, busy, and publicly visible. Now flip it: an org with three dormant repos, two contributors, and no website might score under 30. Same tool, very different read, and a good prompt to check whether the quiet org simply keeps its real work private.
Team Size Benchmarks
| Metric | Elite | High | Medium | Low |
|---|---|---|---|---|
| 1-20 contributors | Startup | Fast iteration | Limited bandwidth | Bus factor risk |
| 20-100 contributors | Sweet spot | Growing fast | Scaling pains | Process gaps |
| 100-500 contributors | Well-scaled | Complex org | Coordination heavy | Silos forming |
| 500+ contributors | Platform teams | Enterprise scale | Slow decisions | Bureaucracy |
Source: Based on patterns from high-performing engineering organizations · Team size affects velocity, communication patterns, and delivery speed differently at each scale
Our Take
GitHub stars and repo counts are vanity metrics. What actually matters is contributor activity and code velocity.
A company with 5 active repos and 50 regular contributors is likely healthier than one with 500 dormant repos and 10,000 stars on a single project. This tool focuses on signals that indicate ongoing engineering investment.
"Teams with 50-200 engineers have the highest velocity per capita. Below 50, you lack specialization. Above 500, coordination overhead dominates."
— DORA State of DevOps Report
Key terms
- Estimated team size
- The number of unique human contributors found across the org's top active public repos. It is a lower bound - private repo contributors, non-coding roles, and contractors are not counted.
- Active repos (30d)
- How many of the fetched repositories received a push in the last 30 days. A proxy for whether the org is shipping now rather than coasting on old work.
- Health score
- A 0-100 composite weighting team size, recent activity, language diversity, community engagement, and profile completeness. A signal of engineering investment, not a measure of code quality.
- Primary language
- The language declared on the most repositories in the org. GitHub assigns one primary language per repo based on file bytes, so polyglot repos still count once.
- Rate limit
- GitHub caps unauthenticated API use at 60 requests per hour per IP. Because each analysis makes several calls, heavy use can hit the cap until it resets.
Frequently Asked Questions
The estimate is based on unique contributors to the organization's top active repositories. It's a lower bound - actual team size may be larger since it only counts developers who have contributed to public repos. Private repositories, non-coding roles, and contractors are not included.
Want to track this automatically?
CodePulse connects to your GitHub and calculates these metrics in real-time. No more manual data entry or spreadsheets.
Free tier available. No credit card required.
See These Features in Action
Track all four DORA metrics and benchmark against industry standards.
Interactive graph of review relationships and workload distribution.
Learn More
DORA Metrics Explained: The 4 Keys Without the Hype
A complete breakdown of the four DORA metrics - deployment frequency, lead time, change failure rate, and MTTR - with honest benchmarks and gaming traps to avoid.
Engineering Benchmarks {{YEAR}}: Use Them Without Gaming
A practical guide to using engineering benchmarks effectively - choosing the right comparison, setting targets, and communicating to leadership without falling into metric traps.
Lines of Code Is Embarrassing. Measure This Instead
Stop treating engineers like factory workers. Learn why LOC tracking is embarrassing, which metrics destroy trust, and how to measure productivity without surveillance. 83% of developers suffer burnout - bad metrics make it worse.
Related Tools
DORA Metrics Calculator
Calculate your DORA metrics performance tier. Input your deployment frequency, lead time, MTTR, and change failure rate to see how you compare to elite teams.
Engineering Headcount ROI Calculator
Calculate the ROI of your engineering team. See the true cost per engineer and what productivity gains would mean for your bottom line.
Developer Productivity Score Calculator
Calculate your team's productivity score across three dimensions: Efficiency, Effectiveness, and Experience. Get personalized recommendations.