Smiling on the outside?

A health check for your codebase.

Paste a public GitHub repo. Garrick scans it for vulnerabilities, leaked secrets, risky files and missing tests, and scores it from 0 to 100 in minutes.

Scan a repository

Scanning opens soon.

Public repos only We never run your code Reports last 7 days unless you claim them

Garrick, a jester mask smiling with a tear on its cheek

What you get

One report page, readable in under a minute.

An overall score, a score for each area, the files where trouble concentrates, and the three fixes worth making first. Every point lost shows its evidence.

Five scored areas

  • SecurityKnown vulnerabilities, leaked secrets (counts only), risky patterns30%
  • DependenciesHow far behind each package is, unpinned versions20%
  • MaintainabilityComplex functions, duplicated code, codebase size20%
  • TestingTest-to-code ratio, coverage config, tests running in CI15%
  • DeliveryCI, pinned actions, update bots, license, recent activity15%

For information, not scored: hotspots (files that change most and are most complex) and bus factor (files only one person touched this year).

Riskiest files

A short ranked list of the files that changed most this year and are also the most complex, with why each one is risky.

Top 3 fixes

Plain-language actions that name the file or package, ordered by how many points they win back.

Update to lodash 4.17.21: it fixes 2 critical vulnerabilities.

The score

From Royal Court to Off With Its Head.

Every report starts behind the smiling mask, then lifts it to show the repo's real face. The number and the band always come together, and the band describes the repo, never the people who wrote it.

  1. 90–100Royal Court
  2. 75–89Court Favorite
  3. 55–74Still Juggling
  4. 35–54Dropping the Balls
  5. 15–34Thrown in the Dungeon
  6. 0–14Off With Its Head
  7. No scoreJester's Day Off

Jester's Day Off means there is nothing fair to score: a fork, an archived repo, docs only, or too little code. The report says which.

How we treat your repo

We read your code. We never run it.

Static analysis only

No installs, no builds, no running your scripts or config. Our tools use our settings, never the ones in your repo.

Secrets stay counts

If we find possible secrets, the report says how many. Never the value, the file or the line.

Unlisted reports

Each report has its own unguessable link. Search engines don't index it and we don't list it anywhere.

Gone in 7 days

Reports nobody claims expire after a week. Claimed reports stay until the owner says otherwise.

Own the repo? Claim the report.

Sign in with GitHub. If you have maintain or admin access, you can keep the report, share it, rescan when you've fixed things, and add a README badge. Reports of repos you don't own can't be shared.

The README badge

https://garrick.buffones.com/badge/owner/repo

It changes only when you rescan.

Why Garrick?

In Juan de Dios Peza's poem "Reír llorando", the actor David Garrick is the funniest man in London, and secretly sad. A codebase can look fine from the outside, with stars, a tidy README and green CI, and still be hurting.