You write code.
We cover it.

A GitHub-first coverage tool. One workflow step, and every pull request answers the only question that matters — can I merge this?

Add it to any repo
- uses: covallaby/action@v0.1.1
  with:
    files: coverage/lcov.info
    min-patch: 85
The Covallaby wallaby holding a coverage checklist

What lands on every pull request

One sticky comment, updated in place — never spam. Plus named checks, diff annotations, and a CI gate.

covallaby  ·  commented just now

🦘 Covallaby

You're covered.
Project coverage91.4%
Patch coverage96.8%
Requiredpatch 85.0%
Nice jump! Every changed line that can be tested, is. 🎉
842 of 921 lines covered across 47 files · Covallaby

Patch coverage, done right

The number that answers can I merge this: coverage of the lines this PR changed. Comments and blank lines never drag it down.

Fails with a map, not a shrug

“Patch coverage is 72.0%, but 85.0% is required — start with src/payment.ts:44-45.” Never just “coverage failed.”

Native GitHub checks

covallaby/patch and covallaby/project as requirable status checks, a rich Checks-tab entry, and warnings right on the untested lines in the diff.

No account. No token.

It runs in your workflow with the token GitHub already gives it. Nothing to sign up for, nothing to leak, no dashboard you didn't ask for.

Two steps. That's the whole setup.

Your test runner already writes a coverage file. Point Covallaby at it.

# 1. run your tests with coverage (any runner, any language)
- run: npm test -- --coverage

# 2. one step — sticky comment, checks, annotations, gate
- uses: covallaby/action@v0.1.1
  with:
    files: coverage/lcov.info
    min-patch: 85

Works with your stack

Formats are auto-detected from content — no language-specific config.

JavaScript / TypeScript Python Java / Kotlin .NET Swift Go

Reads LCOV · JaCoCo · Cobertura · xccov, all normalized into one model.

The Action is the product

It does nearly everything, standalone. These come along for free.

Also included

A CLI that's genuinely useful

Everything the Action does, on your machine — with a beautiful static HTML report.

  • covallaby report — friendly summary
  • covallaby check — gate on a threshold
  • covallaby html — one-file report, dark mode, search
  • covallaby badge — an SVG badge
Also included

Six languages, four formats

LCOV, JaCoCo, Cobertura, and xccov — auto-detected from content and normalized into one model, so the whole product speaks every stack.

  • No language-specific configuration
  • Merge shards and mixed suites automatically
  • Patch, project, and new-file thresholds
Optional · self-hosted · never required

Want coverage over time? Self-host it.

The Action covers your pull requests without a server. When you want history, a dashboard, and a badge URL — one tiny process gives you the rest. Try it right now, no install:

The Covallaby self-hosted dashboard — coverage history, repositories, and recent activity ▶ Open the live demo

Everything you'd expect from a dashboard

  • Coverage history and trends per branch
  • Pull-request comparisons against the base
  • Directory tree, treemap, and hotspot analysis
  • Live SVG badges for your README

Runs anywhere, owns nothing

  • Built-in SQLite, or point it at your Postgres
  • Fits on a $4 VPS or a Raspberry Pi — ~50 MB RAM
  • Never clones or reads your code — only the coverage files CI posts
  • Docker compose up -d and you're live

Opinionated on purpose

Beautiful by defaultZero config to start. Good-looking output you'll actually read.
Friendly, never shamingCoverage tools should point at the next step, not wag a finger.
Coverage is a floor, not a goalWe measure whether your changes were tested, not whether you hit a magic number. No nagging you toward 100%.
Open source, MITThe Action does nearly everything, standalone. A hosted service will only ever be a bonus.