Repo Reality Check: A Chrome Extension That Flags Suspicious GitHub Stars

The next time you're about to build on a GitHub repository, a new Chrome extension wants to give you a second opinion. Repo Reality Check, now live on the Chrome Web Store, injects a compact panel into every GitHub repository page, scoring it from 0 to 100 based on a range of signals designed to surface hype and abandonment risk.

The extension calculates its trust score entirely in your browser using GitHub's public API. It compares star velocity against repo age, commit count, and contributor count, and samples star timestamps to catch suspicious bursts. It also measures bus factor—how concentrated the commit history is—so a 30k-star project carried by one person doesn't look like a safe bet. Maintenance signals include days since last commit, release cadence, median time-to-first-response on issues, and the open/closed issue ratio. README flags look for affiliate-tagged links, hype phrasing, and badge-stuffing, while the license checker translates legal jargon into a practical sentence about copyleft implications.

Why the timing matters

The tool arrives amid growing suspicion about star inflation in the developer ecosystem. Fraudulent repositories have been caught buying stars to climb rankings, and even legitimate projects can look healthier than they are when a viral post triggers a star spike that isn't backed by real adoption. For developers, stars are a shallow proxy for quality, and Repo Reality Check is part of a larger push to make repository credibility more transparent.

The extension is privacy-focused: no accounts, no analytics, no backend. All analysis happens locally, and requests to GitHub's API are made without authentication unless you opt to paste in a personal access token to raise the rate limit from 60 to 5,000 requests per hour. Pro subscribers ($4/month or $29/year) unlock advanced features, but the free tier is genuinely useful.

The author is careful to frame the score as a heuristic, not a verdict. "It's a prompt to look closer," the FAQ reads. "The score surfaces patterns that correlate with hype or abandonment risk, and every flag shows the raw numbers behind it." For developers evaluating dependencies or deciding whether to contribute, that kind of transparency is valuable—especially when a weekend could be wasted on a project that looks popular but is actually a ghost town.