Hatterdash logo: a brain wearing a derby Hatterdash for what's top of mind

Measuring the felt: reading the diff, blame, coverage and dependencies from GitHub…

PR intelligence for mixed human / agent diffs

Hatterdash — for what's top of mind

Open pull requests arrive faster than review bandwidth, and a growing share of the felt is machine-stitched. Hatterdash authorizes against GitHub, lays every open PR you can access on the bench, and scores the change against main: volume, AI-declared lines, coverage of the added lines, test-bed confidence, known vulnerabilities from OSV.dev, and residual security risk. What it couldn't check, it says. Approve, comment, or close without leaving the last.

Sign-in is by invitation for now, so the real analysis is the place to start.

A stylized brain wearing a brown derby hat

GitHub as the source of truth

A GitHub App that reads your repositories and can write only to pull requests. It lists the open pull requests in the repositories it's installed on that you can also reach. Your token stays in your session.

Finding the grain of the diff

The process never pretends to understand a patch. It ships the unified diff, check runs, and commit trailers to an analyzer that returns structured scores the dashboard can defend in a staff meeting.

Actions that write back

Approve via the Pulls review API, comment on the issue thread, or close the PR. Hatterdash is a visor, not a fork of GitHub's permission model.

How a change is dressed

Two processes, one bench. The diagram is the runtime, not a metaphor for later.

Hatterdash request flow GitHub OAuth into Node, which lists pull requests, fetches diffs, and posts reviews. Node calls the Ruby analyzer, which checks new dependency versions against OSV and links each CVE to cve.org. Engineer browser Node · Express OAuth · inbox · actions EJS dashboard GitHub API GraphQL PRs · REST diff Ruby · Sinatra AI · coverage · confidence static risk OSV.dev new dependency versions CVEs linked to cve.org

What each dashboard answers

  1. Lines versus main. Additions, deletions, net, files, and hunks from the GitHub comparison against the base branch.
  2. AI-declared lines. Every added line is traced by git blame to the commit that last wrote it. Lines from commits with an AI author or co-author (Claude Code, Aider, Cursor) count; undeclared use is never guessed into the number.
  3. Confidence vs the current test bed. CI results, coverage of the added lines, test changes, and outstanding risk, folded into a score out of 100 with every point shown: is this the change you would ship? Anything Hatterdash couldn't read counts as unknown, never as clean.
  4. Coverage on the new code. Measured on the added lines from the coverage reports your CI uploads (lcov, Cobertura, or Istanbul, merged across shards); Codecov's patch figure when that's all there is; otherwise it says no report was found rather than inventing a number.
  5. CVEs. The exact dependency versions the change introduces, read from lockfiles at the merge base and the head, checked against OSV, linked to cve.org, and shown with the version that fixes them.
  6. Risk beyond CVEs. Secrets, eval, string-built SQL, unsafe YAML, weak crypto, over-broad permissions.

Authorize once, review at the speed of the inbox

OAuth Inbox Dashboard approve comment · close