How to get GitHub stars
Most repositories never pass 10 stars—not because the code is bad, but because nobody ever finds them. This guide walks through the tactics that reliably earn GitHub stars: making the repository worth starring, launching in the right channels at the right time, understanding how GitHub trending works, and using real developer mutual support for the cold start.
Most visitors decide whether to star within the first screen of the README. Lead with one sentence that says what the project does and for whom, then show a screenshot, GIF, or terminal demo immediately. If a visitor has to scroll to understand the project, you lose the star.
Structure the README as: problem, solution, quick start, examples. A copy-pasteable install command that works on the first try converts better than any badge wall. Add a comparison section if you compete with a known tool—searchers arriving from that tool's name are your warmest audience.
The first 50 stars are the hardest and the most manual. Share the repository directly with coworkers, communities you already participate in, and developers who face the problem you solve. A personal message explaining why it is relevant to them outperforms any broadcast.
A Show HN post on a US weekday morning (roughly 8–11am Eastern) gives the best odds. Use a plain, factual title—'Show HN: X, an open-source tool that does Y'—and stay in the thread answering questions. A front-page Show HN commonly brings hundreds of stars in a day.
r/programming, r/webdev, r/selfhosted, r/opensource, and language-specific subreddits each have their own norms—read them before posting. Posts framed as 'I built this to solve X, feedback welcome' survive moderation far better than plain promotion. Niche Discord and Slack communities convert even better per reader.
Trending rewards star velocity within a time window, not totals. That means concentrated launches beat slow drips: stacking your Show HN, Reddit posts, and newsletter mentions into the same 24–48 hours can push a repository onto the trending page, which then compounds with organic stars from trending browsers.
A launch post on Dev.to, Hashnode, or your own blog ranks in search long after the launch spike fades. Write for the problem ('how to do X') rather than the project name, and let the repository be the answer. One well-ranked article can feed stars for years.
Each meaningful release is a new reason to post. Maintain a changelog, announce versions with a short demo clip, and re-launch major milestones (v1.0, big features) on the same channels. Projects that look alive keep earning stars from returning visitors.
Submit to relevant awesome-lists, alternative-to directories, and package registries. Add topics/tags on the repository itself so GitHub search and topic pages can find it. These placements are small individually but permanent and compounding.
A repository with 3 stars looks abandoned even if it is excellent, and social proof is exactly what launch visitors check. GithubStarMate lets you exchange stars, watches, and forks with other real developers, so your launch does not start from zero. It replaces the awkward 'please star my repo' DMs, not the launch work itself.
Purchased stars come from throwaway accounts with no activity, are detectable by anyone who inspects your stargazers, and risk being wiped by GitHub's anti-abuse systems. One public callout of fake stars costs more credibility than a low star count ever would.
Check your star history chart after every launch or post. If a channel produced a visible step in the curve, do it again with the next release; if it did not, drop it. Growth tactics compound only when you know which ones actually moved your numbers.
Combine a clear README, direct sharing with your existing network and communities, one coordinated launch (Show HN plus relevant subreddits), and mutual support from real developers for initial social proof. Most projects can reach 100 stars within weeks with this combination.
Trending is based on star velocity, not totals. Depending on the language category, roughly 50–300 stars within a day can be enough for the daily trending list of a specific language.
Stars are social proof, not usage. They matter most at the discovery stage: visitors, potential contributors, and even investors use them as a quick credibility check before reading further.
Asking people who genuinely evaluated the project is normal open-source practice. Mass-DMing strangers or incentivizing stars with rewards violates GitHub's policies and annoys the community.
No. Bought stars come from empty accounts, are easy to expose with a fake star checker, and can be removed by GitHub. Mutual support between real developer accounts is a safer way to build early social proof.
GithubStarMate is a mutual support exchange: you star, watch, or fork other members' repositories from your real account, and other developers do the same for yours. It solves the cold-start problem while your launches and content build organic growth.
Launch spikes always decay. Sustained growth comes from repeated releases, content that ranks in search, directory placements, and being useful enough that developers share the project on their own.