An engineering-health report for your codebase you can attach to the board deck — in under an hour.
RepoHealth reads your repository's public GitHub data and produces a dated, third-party-legible assessment: commit and author activity, author concentration and bus factor, test and CI signal, dependency and README freshness — every number with a note on how it was computed.
See a real report
Read the full sample →A report on the pallets/flask open-source project in the format a buyer receives, framed for acquisition or investment diligence.
The headline finding
93%
of recent commits come from one author
Flask shows a working delivery pipeline with configured CI and a test footprint larger than its source footprint.
Delivery & test signal
133%
test-to-source file ratio
98 commits in the last 12 months; CI configured.
Every number auditable
How we computed this
For up to 8 of the largest top-level directories, the leading author's share of the newest commits touching that directory in the last 12 months, up to 300 commits per directory, and how many authors made those commits. Taken from GitHub's commit list filtered by path.
What's in the report
Six metric areas, computed from the repository's public GitHub data and package registries. Every number comes with a note on how it was computed.
Commit & author activity
How much is changing and who is changing it: the commit count over the last 12 months and the number of active authors.
Author concentration & bus factor
Who the codebase depends on: top-author commit share overall, and bus factor by top-level directory, so you see which directories rest on one person.
Test signal
Whether tests exist alongside the code: the ratio of test files to source files. A proxy for coverage, not a measurement of it.
CI presence
Whether the repository holds a configuration file for a common CI system.
Dependency freshness
For npm and Python projects, how many dependencies in the root manifest have had no new release in 18 months.
README freshness
When the README was last changed — the page a new engineer or acquirer reads first.
Who it's for
Board review
Walk in with a dated, third-party-legible picture of engineering health: activity, continuity risk, and delivery discipline, framed for a non-engineering reader and ready to attach to the deck.
Acquirer diligence
A structured read on the codebase you're evaluating — concentration risk, maintenance signals, and the specific follow-ups worth putting to the sellers, computed from the repo's public data.
Inherited codebase
You've just taken over a repo you didn't write. Get a map of where the risk sits — which directories have one maintainer, what the tests and dependencies look like — before you start changing things.
Pricing
One assessment
$249
One engineering-health report: executive summary, the six metric areas with computation notes, and follow-up questions framed for your situation. Hosted on your own link and emailed to you. Typically ready within an hour. No subscription.
Assess your codebase — $249FAQ
What exactly is in the report?
An executive summary; commit and author activity over the last 12 months; author concentration with bus factor by top-level directory; test-to-source file ratio; CI presence; dependency freshness; the README date; and a short list of follow-up questions framed for your situation (board, diligence, or inheritance). Every number has a note describing how it was computed from the repository's public data.
How do you access the code?
Give the URL of a public GitHub repository. The assessment only reads; it never writes to your repository. Private repositories and uploaded archives are not supported.
How long does it take?
Reports are typically ready within an hour of checkout. You get a hosted report page on your own link and an email with the link.
Is this a code review or a security audit?
No. It's an engineering-health assessment: activity, continuity risk, maintenance and delivery signals. It does not review code correctness line-by-line, find vulnerabilities, or replace a security audit.
What is your refund policy?
If we can't produce a report from the repository you provided — a repository we cannot read, empty history, pipeline failure — the charge is reversed automatically and you'll get an email; no action needed. If our records show you never opened your delivered report, you can request a refund within 30 days using the link in your delivery email. See our Terms for details, or email repohealth@forage.bot.
Building on top of RepoHealth? There's an API — see the docs.