Why your open-source project isn't getting stars (and what to do)

You shipped the project. The README is clear. The code works. You posted it to a few places. And now, three weeks later, you're looking at 12 stars and wondering what you missed. This is the most common experience in open source. It's almost always misdiagnosed.

The problem usually isn't the project. It's the distribution.

Stars are a discovery metric, not a quality metric

Stars measure how many people heard about your project, clicked through, and clicked the button. They correlate loosely with quality, but loosely is the operative word. Stars do not measure whether your project is useful, well-maintained, or worth using. They measure how loud your launch was. This means "why isn't my project getting stars?" is usually the wrong question. The right question is: how many people are actually finding it? If the answer is 50, the problem is reach. If the answer is 5,000 with a 0.2% star rate, the problem is a weak README or unclear value prop.

The discovery problem

Most open-source projects are findable on GitHub only by people who already know to search for them. That's a tiny addressable market. The channels that actually drive discovery:

• GitHub topics. If your repository has the right topics tagged, it shows up in topic search results. Add 5–10 relevant topics in the repo settings. This is free and most people skip it. Browse developer-tools, Rust, or Go leaderboards to see which tags have active audiences.
• Search engines. Your README is a landing page. If it contains the words people search for when they have the problem you solve, you'll rank. If it's just a technical specification, you won't.
• Persistent leaderboards. Platforms like RepoRanker keep your listing visible over time, not just on launch day. The leaderboard keeps your project findable to people browsing your category weeks after you stopped actively promoting it.
• Community word-of-mouth. Slow to build and can't be hacked. But one person in a relevant Discord mentioning your project to someone with a specific problem is worth 100 drive-by star-clickers.

The launch timing problem

Most projects are launched once, to whatever audience the maintainer had on that day. If that audience was small, the launch generated nothing and the maintainer concluded the project had no market. A better model: treat the launch as the start of a 30-day campaign. Post on Day 0, then again on Day 7 with what you learned. Day 14 with a shipping update. Day 30 with a retrospective. The second and third posts often outperform the first because they're backed by a real story: real usage, real feedback, real iterations.

What to do right now

1. Add GitHub topics. At least 5. Go to repo settings → Topics.
2. Rewrite your README first paragraph. Answer: what does this do, who is it for, and why use this over the obvious alternative? Three sentences, no more.
3. Submit to a persistent leaderboard. Submit to RepoRanker for free and get on a platform that keeps you discoverable over time.
4. Write one substantive review of another project in your space. On RepoRanker this earns credits you can spend on a visibility boost for your own repo — and it gets your profile in front of the community in a way self-promotion doesn't.
5. Post a "shipped this, here's what I learned" thread on HN, Twitter, or a relevant subreddit. These tend to outperform "I made a thing" posts because they're honest about the process.

The patience problem

Most projects that find an audience do so not on launch day but somewhere between weeks 4 and 12. This is when search traffic accumulates, word-of-mouth referrals land, and the first independent contributor shows up. Projects that give up at week 3 never find out what would have happened at week 6. The goal of a leaderboard listing isn't to get 1,000 stars overnight. It's to make sure your project is still findable in three months.

Submit your repo for free and stay discoverable past launch day.

Related: GitHub stars don't measure quality · Where to submit your open-source project · How RepoRanker works.