How to Tell When a Repo's Star Count Isn't Telling the Truth

A repository currently sitting near the top of GitHub Trending reports 235,000 stars — acquired in six months, by a single maintainer, on a project with a paid tier attached. The stars are not the number to check. Pull the repo through the REST API and look at ratios instead. Watchers against stars is the most useful: healthy large projects generally sit between 1.5% and 4%, and this one is at 0.52%. Forks against stars runs 5–10% for a popular tool; this one is at 15%. Open issues are another tell — a genuinely 235,000-star project generates issue volume in the thousands, not double digits. None of this proves manipulation, and the underlying project may be perfectly good. But high forks with low watchers and thin issue traffic is the specific fingerprint that campaigns produce and organic growth does not, because stars and forks can be manufactured while notification subscriptions and real bug reports cannot. Judge the code, not the badge.