# GitHub authentic star quality before star buying

> Protect GitHub trust by earning real stars and visible usage instead of buying a short-lived popularity signal.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-authentic-star-quality-before-star-buying/
- Source: [arxiv.org](https://arxiv.org/abs/2412.13459)
- GrowthDex source hub: [arXiv: Six Million Suspected Fake Stars in GitHub](/sources/arxiv-six-million-suspected-fake-stars-in-github-arxiv-org/)
- Last checked: 2026-06-10T06:39:08.000Z
- Rarity: rare
- Budget: free
- Channels: GitHub, Developer Trust, Open Source
- Stages: authentic stars, developer trust, fake stars, open-source credibility, GitHub reputation


## Why this can grow

GitHub stars are useful because developers treat them as a weak trust signal. That signal breaks when the pattern looks fake. The StarScout paper studied suspected fake stars across GitHub metadata from 2019 to 2024 and found fake-star activity surged in 2024. It also found fake stars were often used for phishing malware and other short-lived promotions, with any growth-hacking benefit lasting less than two months before becoming a long-term liability. The founder lesson is blunt: do not poison the repo's trust graph. Real HN attention, contributor activity, issues, examples, and external mentions age better than a bought number.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where github authentic star quality before star buying can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the GitHub and Developer Trust channel.
3. Use the evidence from arxiv.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

The StarScout study reports a rapid surge in suspected fake-star activity in 2024 and says fake stars can create short-term promotion but become a liability in the long term.

## Adjacent tactics in the same lane

- [HN repo ready before community attention](/growth-ideas/hn-repo-ready-before-community-attention/) - 2 shared channels
- [GitHub release notes categories match the upgrade job](/growth-ideas/github-release-notes-categories-match-the-upgrade-job/) - 1 shared channel, 1 shared stage
- [Resend open-source wedge before core product pitch](/growth-ideas/resend-open-source-wedge-before-core-product-pitch/) - 1 shared channel, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The public room should be ready before attention arrives](/blog/the-public-room-should-be-ready-before-attention-arrives/) - community-led growth, launches, brand trust
- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) - Hacker News, GitHub, developer marketing

## Reading path: AI products

- [The public room should be ready before attention arrives](/blog/the-public-room-should-be-ready-before-attention-arrives/) (2026-06-10T07:06:20.000Z)
- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) (2026-06-10T06:39:08.000Z)

## Reading path: developer tools

- [The public room should be ready before attention arrives](/blog/the-public-room-should-be-ready-before-attention-arrives/) (2026-06-10T07:06:20.000Z)
- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) (2026-06-10T06:39:08.000Z)

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.