What is the difference between GitHub stars and forks?

Starring is one input. Someone hits the star button, the repo drops onto their stars list, and your star count ticks up by one. Nothing gets copied. It's a bookmark with a public counter attached.

Forking is a copy. The fork button clones the entire repo (code, history, branches) into a new repo under their own username, like dev-priya/rocketdb spun off your acme/rocketdb. Now they own a working copy they can edit, run, break, or open a pull request from. See how to fork a GitHub repo for the full route.

So: a star touches a list. A fork spins up a whole new repo. Same button row, very different weight.

Not worth more. Different. The honest way to read them is effort and intent, and those two sort themselves the second you look.

Effort. A star costs one click and a second of attention. A fork costs a decision: I want this code in my account. One is a reflex, the other is a small commitment. That gap is the whole story.

Intent. A star says I might come back. A fork says I'm going to use or build on this. Neither is a promise (plenty of forks go stale, plenty of stars never reopen the repo), but if you're ranking who actually did something, the fork sits higher. You're going to see way fewer forks than stars. That's normal. That's the route, keep going.

Depends on what you're chasing: reach or intent.

Stars are reach. The headline number, the social proof in the README, the thing a stranger checks before they trust your project. It's aggregate: how many people nodded. Good for momentum, trending, and first impressions.

Forks are intent. Fewer of them, but each one is someone who wanted your code in their hands: builders, integrators, the people most likely to file an issue or ship on top of you. If you're counting, watch stars. If you're hunting the humans who'll actually use the thing, forks punch above their number.

News first. In 2026 GitHub restricted the public stargazers list on repos you don't own, and the old /stargazers view got locked down. That's the fact you're working with now. More on that in did GitHub remove the stargazers page?.

The forks list stayed public. So for a repo you do not own, forks are the readable who-signal: you can still see the usernames that forked it. That's a real shift. Before 2026 stars were the easy public read, now the fork list is the one still open. See who forked a GitHub repo walks the exact spot.

Owner-first, and this is the important part: for your own repo, none of this touches you. Your stargazers are your data and you keep full access to them. The restriction is about other people's repos, not yours.

Both are usernames underneath. A star count is aggregate (how many nodded). A fork count is aggregate (how many copied). The counts are the scoreboard. The usernames are the value, because a username is a person.

Open one and it's a GitHub profile: a name, sometimes a company, sometimes a couple of links, and a public email for many of them. That's how a number like 1,200 stars turns into someone specific, like dev-priya who forked acme/rocketdb.

For your own repo, that's the whole move: warmstars takes your own stargazers and turns them into named people, from public data only, never strangers' repos. Start with the free stargazer checker, then pull the full list of who starred your repo.

The count is the scoreboard. The people are the run. Gg.