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.
Enter any public GitHub organization to get instant insights into their engineering team. See estimated team size, activity levels, tech stack, and more—all from publicly available data.
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.
Enter a GitHub organization name above to analyze their engineering metrics.
Try popular orgs like , , or
"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
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
How This Works
Fetch Public Data
We query GitHub's public API for org metadata, recent repositories, and contributor lists.
Aggregate Metrics
Unique contributors are counted across top repos. Activity is measured by recent pushes.
Score Health
A composite score weights team size, activity, language diversity, and community engagement.
Frequently Asked Questions
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
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.
Learn More
DORA Metrics Are Being Weaponized. Here's the Fix
DORA metrics were designed for research, not management. Learn how to use them correctly as signals for improvement, not targets to game.
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.