Is this GitHub repository actually maintained?
Stars tell you a project was once interesting. They tell you nothing about whether anyone still maintains it. Enter any public GitHub repository to get a free 0–100 health score built from maintenance recency, bus factor, issue and pull request responsiveness, release cadence and community files — so you can tell a maintained project from an abandoned one before you depend on it.
What the GitHub repository health checker looks at
In plain terms: the analyzer checks how recently the project was pushed to, whether its documentation is complete, how quickly issues and pull requests get a response, how many people actually author the code, and how often it ships releases — then combines all five into one score and explains, in plain language, exactly why it landed where it did.
Why GitHub stars don't tell you if a repository is maintained
A GitHub star is a one-way vote that never expires. A project can collect fifty thousand of them during a hype cycle, lose its only maintainer two years later, and still look identical on the badge in your README. Fork counts have the same problem. Neither number decays, so neither one answers the only question that matters when you are about to add a dependency: will this still be maintained in twelve months?
The signals that do answer it are unglamorous and scattered across half a dozen API endpoints — when the last commit landed, whether releases still ship, how long a pull request sits before anyone looks at it, how many people are actually authoring the code, and whether the basic community files exist at all. This tool pulls those together and scores them, so the judgement takes ten seconds instead of ten minutes of clicking through tabs.
The score is intentionally unkind to popular-but-stale projects. If a repository with a large following comes back with a D, that is the tool working correctly, not a bug.
How the GitHub repository health score is calculated
grades: a 85+ · b 70+ · c 55+ · d 40+ · f <40