Free tool
Is this open-source project still healthy? — free health check for any public GitHub repository
Paste a GitHub repository. We read five signals from GitHub's public data, in your browser, and show the verdict with the working.
Or try one
Nothing you type is sent to us. Your browser asks GitHub directly. A check costs about 7 of the 60 free requests GitHub gives you an hour.
Sample reading · recorded 13 Oct 2026
Healthy
Work lands most weeks, and nothing we read is weak.
- CommitsDoes work keep landing?
- SteadyStrongLast commit today · a commit in 52 of 52 weeks · 8,094 commits in the year
- PeopleDoes one person carry it?
- Spread outStrong4 people wrote half of 105 code commits · most: mihir-kandoi (33%)Left out: 2 bot commits, 58 merge commits, 35 docs, chore, CI or test commits
- HandlingAre issues and pull requests handled?
- Kept upStrongIssues: 931 closed, 498 opened in 90 daysPull requests: merged in a median of 23 hours over 76 merged pull requests from people
- RepliesDoes someone answer?
- Not read yetPress Look closer to read a dozen recent issuesReads up to 12 recent issues. Costs up to 12 more of your free requests.
- ReleasesDoes it ship?
- RegularStrongLast release 6 days ago · 30 or more in the year · usually 1 day apart
Recorded from GitHub's public data, so nothing was requested from your browser. Press Check project to read it live, or type or pick another project.
Five signals, each read against a visible line
CHAOSS names these metrics but gives no cut-offs. The lines below are ours: rules of thumb, not tested against projects that later died.
What it reads. Days since the last commit on the default branch, and the weeks with a commit in the last year.
The idea is the OpenSSF Scorecard's: its top score is a commit every week for 90 days. The lines are ours.
frappe/erpnext: Strong
What it reads. The smallest number of people behind half of the code commits, from a sample of up to 200 across the year.
The metric is CHAOSS's: the smallest number of people behind half the contributions. The lines are ours.
Read only when at least 20 commits count.
In a study of 133 popular projects, 65 % had a truck factor of two or less: the work rests on very few people.
frappe/erpnext: Strong
Check a whole stackIdea from CHAOSS, Contributor Absence Factor
What it reads. Issues closed per issue opened over 90 days, and the median days to merge a pull request from a person.
CHAOSS defines this ratio for pull requests; we apply it to issues and time pull-request merges instead. Both lines are ours.
Issues read only when at least 20 were opened; pull requests when 5 merged ones are in the sample.
frappe/erpnext: Strong
What it reads. Of a dozen issues opened 7 to 45 days ago by people outside the team: how many got a team reply, or were closed, within a week.
The metric is CHAOSS's: time to first response, which we sample from a dozen issues instead of measuring all of them. The lines are ours.
Read only when at least 8 issues qualify.
frappe/erpnext: not read yet
What it reads. Releases in the last year, days since the last, and the usual gap between them.
The metric is CHAOSS's: the count of releases. The lines are ours.
Not read when the project publishes no GitHub Releases.
frappe/erpnext: Strong
Before any grade, the first of these that applies is the verdict:
- Archived or disabled on GitHubArchived
- No commits at allNothing to read
- Created under 90 days agoToo new
- Last commit over 365 days agoDormant
- Last commit over 180 days agoStalled
- Fewer than 3 signals could be readNot enough to judge
Otherwise it grades: Slowing, Several weak spots, Healthy with things to watch, or Healthy.
What this check answers
Whether an open-source project is still looked after, from its public record.
Your browser asks GitHub directly, and nothing you type is sent to us. A healthy record is not a promise about the future; it is the evidence there is today.
What it rests on
- GitHub's public APIReleases, commits, issues and contributors, read in your browser.
- The verdictEach signal's reading and threshold are shown under it.
What a good reading does not tell you
Six things the five signals cannot see. Read them before you rely on a verdict.
- FitA healthy project can still be wrong for your business.
- Quiet is not deadA finished library has few commits and still works. It reads as weak here.
- Work done elsewhereForums, ticket systems, GitLab and mailing lists are invisible. So are releases shipped through npm or PyPI.
- Money and controlWho pays the maintainers, who owns the company, whether the licence can change: not read.
- SecurityHow fast a flaw gets fixed is a different check. The OpenSSF Scorecard reads it.
- The futureNothing here is tested against projects that later died.
Who made this
We implement ERPNext and Medusa for clients and support Odoo, and earn from that, so we are not neutral about them. Each is read by the same rules as any other project, and every request is listed so you can check us. We are Frappe specialists; how we stay independent is in this essay.
When the answer is a project
When you decide to run on open source, someone has to look after it. These are the next steps.
Talk through your stack
Bring the projects you checked; we say what we would watch.
Managed hosting
Open-source software on servers you own, updated and watched by us.
Our open-source work
What we have contributed upstream, and where.
Questions about the check
The one most people ask is answered first. Type to find the rest.
Why is there no single score?
The reading
Using it