28,859 stars (72%) arrived in the first 6 days — peaking at 8,369/day on day 2. For a niche job-search CLI tool, this is far beyond organic viral growth patterns.
The GitHub REST API for stargazers is capped at 40,000 records — the remaining 14,144 (26%) cannot be retrieved through it. This is a known API limitation, not evidence of purging. The total count of 54,144 from the repo endpoint is authoritative.
19.8% — nearly 1 fork for every 5 stars. Healthy open-source projects average 1-5%. This is a hallmark of fork-for-star schemes ("fork mine and I'll fork yours").
Only 207 watchers on 54k stars (0.38%). Normal projects see 1-5% watcher/star ratio. This pattern indicates one-and-done actions — typical of bots or star-network participants.
Sampled 200 stargazers: 27.5% have 0 followers, 12.5% have 0 public repos, 8.5% are fully empty (0 repos, 0 followers, 0 following). 17.5% are low-quality (≤1 repo, ≤2 followers).
The repo was featured in WIRED and Business Insider, which may have driven some organic stars. However, the magnitude and pattern are inconsistent with typical viral growth from press coverage.
The combination of explosive launch, abnormal fork/star ratio, low watcher ratio, and poor account quality strongly suggests the use of star-for-star / fork-for-star networks to artificially inflate popularity. Some stars are likely organic (post-WIRED/BI coverage), but a significant portion is almost certainly inauthentic.
This report was generated using StarScout — a fake star detection framework published at ICSE 2026. Data collected via the GitHub REST API. Full dataset available at github.com/hehao98/starscout.
The repository was created on April 4, 2026, after the StarScout dataset cutoff (Jan 1, 2025), so it is not in the published dataset. For precise detection, run StarScout locally against this repo.