GitHub star-for-star: is it allowed, and what works instead?

Star-for-star (also “S4S”, “star exchange” or “star back”) is any deal where people star each other’s repositories in return, not because they use or like the project. It shows up as group chats and forum threads, credit-based exchange sites where starring others earns stars for your repo, and paid services that sell stars in bulk.

It’s tempting because stars are social proof: they help a repo look trustworthy and can nudge it towards GitHub’s Trending page. That’s exactly why GitHub protects them.

GitHub’s Acceptable Use Policies (section on spam and inauthentic activity) don’t allow:

• “inauthentic interactions, such as fake accounts and automated inauthentic activity”, including rank abuse “such as automated starring or following”;
• “coordinated inauthentic activity”;
• “creation of or participation in secondary markets for the purpose of the proliferation of inauthentic activity”;
• activity that is incentivized by, or incentivizes inauthentic engagement with, rewards.

A star exchange is a secondary market for stars, and star-for-star is coordinated, incentivized starring. It doesn’t matter that real people click the button: the stars aren’t a genuine signal that someone found the project useful.

GitHub doesn’t publish how it detects abuse, and nobody outside GitHub can tell you the exact rules. But trading leaves obvious patterns, the kind researchers have used to find fake-star campaigns at scale:

• the same group of accounts starring the same set of unrelated repos;
• sudden bursts of stars with no matching visits, forks, issues or pull requests;
• starring accounts with little activity of their own.

Anyone can also check a repo’s star history in seconds. A spike that no launch or post explains is a red flag to the developers you actually want as users.

• Stars removed. GitHub can strip inauthentic stars, so the number you traded for disappears.
• Repos flagged or hidden, and in serious cases accounts restricted or suspended.
• Lost trust. Developers who spot a faked star count assume the rest of the project cuts corners too.

Even when nothing happens, traded stars don’t bring what you wanted: no users, no issues, no contributors.

Stars follow attention. The reliable way to get them is to put a good project in front of the developers it’s for, and let the ones who like it star it on their own:

• Make the repo worth landing on: a README that says what it does in one line, a screenshot or GIF, and a quick start. See how to get your GitHub project discovered.
• Launch where developers already are: Show HN, Reddit, dev.to, Product Hunt and communities for your language. See where to promote your open-source project.
• Tell a story in every post: the problem you had and why you built this, not “please star”.

No, and it’s built not to be. Stardeck shows your repo to developers who choose to look at it, and they like it on Stardeck if they’d actually use it. There’s nothing to trade:

• nobody can see who liked their project, so there’s no one to “pay back”;
• the leaderboard counts likes on Stardeck, never GitHub stars, and likes are capped at 10 a day;
• pitches that ask for stars or follows back are rejected automatically.