GitScore analyzes public GitHub data to produce a score out of 1000 that summarizes a developer's visible open-source activity and reach. This post explains what goes into it, how the categories work, and just as importantly, what the score cannot tell you.
What data GitScore uses
Everything comes from GitHub's public API, with no login or private data:
- Your public profile: followers, public gists and account creation date.
- Up to 500 public repositories you own, including their stars, forks and primary language. Forks of other people's projects don't count.
- Your last year of contributions, the same data as your GitHub contribution graph: commits, pull requests, reviews, issues and which weeks you were active, plus how many of your pull requests were merged into other people's repositories.
If contribution data isn't available, activity is estimated from your recent public events, which GitHub keeps for 90 days. The score page tells you when that happens.
The six categories
Activity & Consistency (350 points)
Based on your last year of contributions. Consistency, the share of the last 52 weeks with at least one contribution, is worth up to 100 points. Pull requests merged into other people's repositories are worth up to 100, because someone else reviewed and accepted the work. Commits (up to 60), code reviews (up to 50), pull requests opened (up to 20) and issues (up to 20) make up the rest.
Community Impact (300 points)
Measures how much others use your work: total stars on your original repositories (up to 220), their forks (up to 60) and public gists (up to 20).
Projects (150 points)
Mostly rewards how many of your original repositories have reached 10 stars (up to 110), with a smaller amount for the number of original repositories (up to 40). Ten useful projects count for far more than a hundred empty ones.
Social Influence (100 points)
Based on followers. How many accounts you follow doesn't affect your score.
Languages (50 points)
10 points for each programming language in which at least one of your repositories has earned a star, up to 5 languages. Markup and notebook formats such as HTML, CSS and Jupyter Notebook don't count.
Account Longevity (50 points)
5 points per year since you joined GitHub, measured from your exact join date, up to 10 years.
Why stars and followers use a logarithmic scale
Stars, forks, followers, gists and contribution counts are scored on a logarithmic scale. Going from 0 to 100 stars earns as many points as going from 100 to 10,000. This keeps the score meaningful for both newer developers and maintainers of hugely popular projects, and means early growth is rewarded the most.
Grades
Your total maps to a grade: S+ (900+), S (800+), A+ (700+), A (600+), B+ (500+), B (400+), C+ (300+), C (200+), D (100+) and F (below 100). Separately, your rank shows how you compare with a random sample of about 1,000 GitHub accounts that have at least one public repository. The median account scores around 40, so a score of 85 is already in the top 15% and 309 is in the top 1%.
What the score can't measure
The score only sees public GitHub activity. It can't see private or company work, code quality, contributions on other platforms like GitLab, or the impact of work that doesn't produce stars. Work in repositories owned by an organization only counts through your contributions, not through that repository's stars. Treat the score as a conversation starter and a way to track your own progress, never as a measure of someone's ability or as a hiring decision.
See it in action
Check any username, read the full methodology, or compare two developers side by side.