Type a GitHub username and calculate its GitHub score in seconds. See stars, forks, repositories and the language split on one screen, and find out where the profile falls short. A free GitHub score checker with no sign-up that runs entirely in your browser.
This profile has a lot of repositories, so the GitHub score is based on the 300 most recently updated ones.
Paste a GitHub username or profile link into the box. It works on your own profile and on anyone else's.
The tool reads the profile and its public repositories, grades five subjects and turns them into a single letter.
The profile health list names each gap in turn: bio, README, licence, descriptions and how recently things were touched.
Download your scorecard as a PNG or copy its link. Whoever opens the link sees the same GitHub score.
A GitHub score reduces a developer's open source trail to a single grade: how many repositories they have opened, how many stars and forks those collected, which languages they work in and how well they keep their projects. This tool reads the same data and turns it into a scorecard — the table of stars, forks and repository counts that is often called a GitHub scoreboard.
For most developers a GitHub profile is a second CV. Hiring teams do look at public repositories, and they care less about star counts than about whether the projects can be understood at all. A pile of repositories with no description, no licence and no commit for years gets in the way of even good code.
The GitHub score checker on this page runs entirely in your browser. The queries go to GitHub over your own connection, nothing is stored on our side and you never have to sign in.
Five subjects are each scored out of 100 and then averaged by weight. Counts such as stars and forks are read on a logarithmic scale: the tenth star says more than the thousandth.
| Subject | Weight | What it looks at |
|---|---|---|
| Popularity | 25 | The stars the repositories collected and the profile's follower count. |
| Output | 25 | The number of repositories that are not forks, meaning the ones actually started here. |
| Upkeep | 20 | The share of repositories carrying a description, a licence and topic tags, plus the share updated in the past year. |
| Reach | 15 | How many forks the repositories received, which is other people building on this code. |
| Variety | 15 | The number of distinct programming languages across the repositories. |
Most of the weight sits deliberately on the subjects you control. Popularity depends largely on luck and visibility, while output and upkeep are the direct return on your own work.
Commit count does not go into the GitHub score. Without authentication GitHub does not hand out a reliable commit history: on some profiles the activity feed comes back empty. Rather than show a number that would be wrong, the metric is left out.
| Score | Grade | What it means |
|---|---|---|
| 90 - 100 | S | A profile that reached a wide audience and is both productive and well kept. Rare. |
| 80 - 89 | A+ | A strong open source trail, with a few projects that drew real attention. |
| 70 - 79 | A | An experienced profile that ships regularly and keeps its projects tidy. |
| 50 - 69 | B / B+ | The foundation is solid. Adding descriptions, licences and tags lifts the grade quickly. |
| 30 - 49 | C / C+ | The profile exists but the shop window is missing. Bringing a few projects forward makes a difference. |
| 0 - 29 | D | A new profile, or one nobody has visited in a long time. A profile README is a good place to start. |
Create a repository named after your username and put a README in it. It is the first thing a visitor sees, and the fastest win available.
A repository with no description is an empty line in search results and on your profile. One sentence is enough to say what the project is for.
Code without a licence is, strictly speaking, code nobody may use. Adding something like MIT takes one click and makes the project usable.
Topic tags make repositories visible in GitHub search and discovery. The right tag is the cheapest route to new stars.
You can pin six repositories to your profile. Choose the work you would actually talk about, not the scratch repositories.
Archive the repositories you will not touch again. Instead of a pile that looks abandoned, visitors see projects that were closed on purpose.
No token, no login. It reads public profile data only and keeps none of it.
Five subjects become a single grade, and the formula is written out on this page rather than hidden in a black box.
It does not just hand out a score: it names exactly what is missing and shows how to fix it.
Download your scorecard as an image you can post, or simply copy its link.
See how many repositories sit in each language. That is where you find out whether how you describe yourself matches what you actually write.
Every calculation happens in your browser. There is no server sitting in between, so the result lands in a couple of seconds.