How the ranking works

What gets counted

An account's stars are the stars on every public repo it owns, added up. Forks don't count, and nor does anything you've only contributed to. For accounts with more than 1,000 repos we count the 1,000 most starred, which covers nearly all of it.

Ties share a rank, so two accounts on the same count are both 7th and the next one is 9th. Users and organizations are ranked separately. The tables list the top 5,000 of each, 50 to a page, and every profile shows its rank and how near the top it sits, wherever that is.

How fresh it is

We find accounts through GitHub's search, by looking for every repo with 50 or more stars, about once a week. Accounts with 1,000+ stars are recounted daily, 100+ weekly and the rest monthly. The rankings themselves are rebuilt every six hours, and each page says when its numbers were last updated.

Not here yet? Sign in and visit your own page, and you're counted on the spot. Opening any profile that's more than a day old also moves it to the front of the queue.

Privacy

Everything here is public data GitHub already shows. Signing in asks GitHub for no extra permissions: we use the token once to count your own public repos, then hand it straight back. It's never stored. Your session cookie only holds your GitHub id and login.

Want off the list? Sign in, open your page and use "Remove me". That deletes your repos, name and follower count from our tables and stops us crawling you again. If you change your mind later, open an issue.

Pages load a cookie-free visit counter from our own Plausible.

Crashes go to our own error tracker, with sign-in codes stripped out first.

Where it came from

This is a rebuild of gitstar-ranking, which ran for years until it shut down in November 2026. Same idea and layout, new code. It's open source too, at NotAFlightRisk/git-star-ranking.