Find The Gaps / a free tool by Doc Holiday

Your docs are wrong.
Find out where.

Find the Gaps compares your code and docs side-by-side, and shows you everywhere they’ve drifted apart — the missing pages, the dead links, the silently wrong examples — before your customers find it first.

View on GitHub

install brew install sandgardenhq/tap/find-the-gaps

❖ 127.0.0.1:8080/bun

Find the Gaps · bun

sections Mapping Gaps Screenshots repo bun v1.1.34

bun / mapping

bun

Bun is a fast, all-in-one JavaScript & TypeScript runtime — a drop-in replacement for Node with a built-in package manager, test runner, and bundler.

Generated 2026-04-30 19:20 UTC

At a glance

65 features identified
0 undocumented (user-facing)
61 drift findings
12 missing screenshots

Sections

Runtime14
Package manager11
Test runner9
Bundler8
HTTP & WebSockets7

bun / gaps

Drift findings

Sorted by severity. Each item links back to the line of code and the docs page it disagrees with.

61 all 22 stale 19 unmapped 20 undocumented

high
Bun.serve({ tls }) stale
Docs show key/cert as strings — code now also accepts BunFile and Buffer.
docs/api/http.md · L142 → src/js/bun/http.ts · L88
high
bun install --frozen-lockfile undocumented
Flag added in v1.1.30. No mention on the install reference page.
src/install/install.zig · L412
med
Bun.password.hash() stale
Docs example uses algorithm: 'bcrypt' — default changed to 'argon2id'.
docs/api/password.md · L24
med
bun.lock unmapped
Page describes bun.lockb (binary). Format is now text-based bun.lock.
docs/install/lockfile.md
low
bun --hot stale
Watcher behavior changed for node_modules. Docs unchanged since v1.0.x.
docs/runtime/hot.md · L60

bun / screenshots

Missing visuals

Pages that describe a UI or output but don't show one. Each entry includes a suggested alt text and where to drop the image.

⌥ needs visual

install/cache.md "Cache directory layout under ~/.bun/install"

▤ needs visual

test/runner.md "Test runner output with --coverage"

◧ needs visual

bundler/dev.md "Devserver overlay on a runtime error"

◑ needs visual

runtime/repl.md "Bun REPL with TypeScript autocomplete"

+ 8 more

on this pageAt a glanceSections

The Problem.

Link checkers catch broken URLs. Spell checkers catch typos. Neither can tell you that a function signature in README.md no longer matches the code — or that a new public API shipped last month without a single page describing it.

Find out before your customers do.

Here's how it helps.

Find

See every gap, instantly.

Find the Gaps compares your code and docs, and points out exactly where they’ve stopped agreeing.

Fix

A report, not a mystery.

You get a plain-language report: here’s what’s missing, here’s what’s pointing at nothing, here’s what no longer matches reality.

Build

Docs that match the product.

You could fix it on your own, or let Doc Holiday do it for you: perfect docs, always.

Three artifacts. One run.

●mapping

An inventory of what your product actually does.

Every feature in your codebase, grouped and described in plain English.

65 features mapped
generated 2026-04-30 · grouped into 8 sections

●gaps

A prioritized punch-list of doc problems.

The undocumented code, the pages pointing at things that don’t exist, and — the worst kind — the docs that look right but quietly disagree with the code.

61 drift findings
undocumented · unmapped · stale

●screenshots

The visuals your docs are missing.

Every place your docs describe a UI but don’t show one — with the exact alt text and insertion hint your team needs to fill it in.

12 missing screenshots
each with alt text · location · caption

Two commands.
A full picture of your docs.

~/workspace — ftg analyze → ftg serve

→ find-the-gaps git:(main) ftg analyze --repo ~/workspace/bun --docs-url https://bun.com/docs 2026/05/01 14:43:31 INFO scanning repository path=/Users/brittcrawford/workspace/bun scanned 9,463 files, skipped 1,672 (defaults: 1,607, .gitignore: 65) 2026/05/01 14:43:38 INFO crawling https://bun.com/docs ✓ mapping 65 features identified ✓ gaps 61 drift findings ✓ screenshots 12 visuals missing → find-the-gaps git:(main) ftg serve bun serving .find-the-gaps/bun/site at http://127.0.0.1:8080/

      ● 13 languages · tree-sitter
      ● tiered LLM pipeline
      ● reads the live docs site — no CMS access
      ● outputs static HTML · markdown · JSON
    

View on GitHub →

Drop it into your CI pipeline.

Ships as a composite GitHub Action. Run it on a schedule, before a release, or on demand. It opens a labeled tracking issue with the findings.

✓ Linux x86_64 ✓ Two required inputs ✓ Auto-opens issues ✓ MIT licensed

View on GitHub →

.github/workflows/find-the-gaps.yml

# Run weekly, file an issue with findings name: find-the-gaps on: schedule: - cron: '0 9 * * 1' workflow_dispatch: jobs: analyze: runs-on: ubuntu-latest steps: - uses: actions/checkout@v6 - uses: sandgardenhq/find-the-gaps@v1 with: docs-url: https://docs.ftg-example.com anthropic-api-key: ${{ secrets.ANTHROPIC_API_KEY }}

Find the Gaps tells you what's wrong.
Doc Holiday fixes it.

The CLI is the diagnosis: a clear, structured list of every place your docs and code have drifted apart. Doc Holiday is the treatment: it picks up that report, opens pull requests against your docs site, and keeps it from happening again.

Book a Doc Holiday demo How Doc Holiday works

Find the Gaps

Diagnoses the drift.

Open-source CLI. Runs in CI or on your laptop. Outputs a structured report.

scans 13 languages
maps features → docs
flags drift, gaps, ghosts

handoff

Doc Holiday

Treats it, automatically.

Hosted service. Reads the report. Drafts the fixes. Files PRs against your docs.

auto-PRs to your docs repo
keeps docs in sync as code ships
works with your existing CI pipeline

Ready to see what your docs are missing?

Free to install and run on any repo. Or let us show you what Doc Holiday does with the findings: automatic PRs, continuous sync, the works.

View on GitHub Book a demo