GitHub Star

GitHub is the world’s largest platform where programmers store the source code of their software and work on it together. Every single project has its own page there, referred to in technical jargon as a repository. On this page, in the top right corner, there is a button with a star. Whoever clicks it gives a star: the project ends up on a personal watchlist, and the publicly visible counter jumps up by one. Originally, this was only meant as a private bookmark. Today, the number next to the star is read by many people as a rating, even though it technically is not one.

Stars as the currency of the open-source world

A great deal of software is open source, meaning it’s freely viewable and usable by anyone. For such projects, there are no sales figures and no revenue from which success could be gauged. The star count is therefore often the only number that is immediately visible. It has developed into a kind of unofficial currency.

For developers, this is tangibly relevant. Anyone choosing between two tools often looks at the stars first. A project with 60,000 stars seems safer than one with 30 – one assumes that many eyes are watching it and that bugs are noticed more quickly. Companies also use the number: in job applications and investor presentations, star counts regularly appear as evidence of reach.

But that’s exactly where the problem lies. A star costs nothing and commits to nothing. One can mark a project without ever having used it. There is even a trade in purchased stars, where fake accounts click en masse. Researchers have documented such campaigns across thousands of repositories. A high star count therefore proves attention, not quality.

What happens when you click the star

Technically, a star is simply an entry in a database: user X has marked project Y. This requires a free GitHub account. An account can only give one star per project, and it can be removed again at any time. The counter then goes back down as well.

It’s important to distinguish it from two similar buttons next to it. A fork creates one’s own copy of the project, which one can then continue working on independently. Watch subscribes to notifications about every change. The star does neither – it is purely a marker. In the past, it was actually tied to a subscription, but since 2012 the functions have been separated.

Stars also feed into GitHub’s rankings. Projects that collect many stars in a short time appear in the so-called Trending section on the homepage. This creates a snowball effect: visibility brings stars, stars bring more visibility. That’s why some teams deliberately try to get their project placed there.

Star counts in AI headlines

This phenomenon is especially striking in artificial intelligence. When the image program Stable Diffusion and later tools like AutoGPT appeared, they collected tens of thousands of stars within a few days. Tech media reported this as news: “fastest project ever to reach 100,000 stars.” The number itself thus becomes the event.

The term also comes up on finance pages. When a start-up raises money, the report often includes the star count of its open-source project. It’s meant to show that a community of users already exists before any revenue does. Well-known examples are databases or AI tools that are freely available and make their money with a paid add-on version.

Anyone reading such reports should be able to put the number into context. It makes more sense to look at the trajectory rather than the final figure. Has a project grown steadily for years, or was there a single spike after a viral post? Other metrics are more meaningful anyway: how often the software is downloaded, when someone last worked on it, and how many people contribute regularly.