How to get more GitHub stars (without buying them)

Every star on a GitHub repo is the end of a short chain: someone heard about the project, clicked through, understood it from the first screen, and decided it was worth remembering. To get more stars you either put the repo in front of more people or convert more of the people already landing on it. Everything that works is one of those two. Everything sold as a shortcut skips both, and we will get to why that backfires.

First, fix conversion. It is the cheapest win.

Open your repo in a private window and look at what fits on one screen. That is what a visitor judges. Before you spend an hour on promotion, make sure that screen does its job:

• The description field. The one line under the repo name shows up in search results, on GitHub Trending and in link previews. Say what the project does, not what it is called.
• A one-paragraph pitch. What it does, who it is for, and why it beats the obvious alternative. Our README best practices post covers the structure.
• Proof it works. A screenshot, a short GIF or a terminal recording. People star what they have seen working.
• A one-line install. If trying it takes ten steps, most visitors leave before step two and never come back to star it.
• Topics and a social preview. Add 5 to 10 topics in the repo’s About panel, and upload a social preview image under Settings so a shared link renders as a card instead of a bare URL.
• A polite ask. One line near the end of the README, such as "If this saved you time, a star helps other people find it." Plenty of people who use a project never think to star it.

Then widen reach

A repo with a great first screen and no visitors still gets no stars. Reach comes from a handful of channels, and they work best in sequence rather than all at once:

1. Launch in one concentrated push. Stars that arrive in the same day or two are worth more than the same number spread over a month, because short bursts are what GitHub Trending appears to reward. See how GitHub Trending works.
2. Post where your users already are. The subreddit, Discord or forum for the language or framework your project serves. Read the self-promotion rules first.
3. Show HN, once. A plain title, and a maintainer who answers comments for the first day.
4. Write the post behind the project. "Why I built X" or "How X does Y" on your blog or Dev.to. Posts get shared and indexed in ways a bare repo link never does.
5. Get onto lists that last. Awesome lists, newsletters and persistent boards keep sending visitors after launch week. Where to share your GitHub project covers them one by one.

For the full sequence, read how to promote your GitHub repo. If you have already launched and stalled, why your project isn’t getting stars walks through the diagnosis.

Stars compound, so the early ones matter most

Stars are not only a score. They feed the surfaces that send you more visitors: GitHub Trending, topic pages, most-starred lists and third-party repo rankings all lean on star counts or star growth. That is why the first few hundred are the hardest and the next few hundred come easier. It is also why a project that launches quietly can sit at 30 stars for a year with nothing wrong with the code.

Should you buy GitHub stars?

No. Searches for "buy GitHub stars" and "free GitHub stars" lead to star sellers and star-exchange schemes, and both have the same three problems.

• It breaks GitHub’s rules. GitHub’s Acceptable Use Policies prohibit "rank abuse, such as automated starring or following", and taking part in secondary markets for inauthentic activity. Accounts that sell stars get removed, and the stars they gave go with them.
• It barely works. A study by researchers at Carnegie Mellon and collaborators (He et al., "4.5 Million (Suspected) Fake Stars in GitHub") measured fake starring across GitHub and found fake stars only give a short-term promotion effect and become a liability over the long term. Most of the fake stars it found were propping up short-lived malware repos, which is not company you want to keep.
• People check. Developers click the stargazers list. A wall of empty accounts created the same week tells them more about your project than the number does.

If you want to pay for visibility, pay for it openly

There is nothing wrong with spending money to get a project seen. The problem with bought stars is that they pretend to be something they are not. Disclosed placement is the honest version: you pay, and everyone can see that you paid and how much.

That is how RepoRanker works. Listing is free. A place near the top of the board starts at $3, the price sits on the row that paid it, and the spot holds until another repo spends more. Rows nobody has bought are ordered by stars gained since listing and recent pushes, so real momentum still shows on the board.

List your repo for free, and see the placement ladder for what each position costs today.

Related: How to promote your GitHub repo · How GitHub Trending works · GitHub stars don’t measure quality.