API Docs Drift Checker
Paste any public GitHub repo below and Verlio scans its most recent merged pull requests to show you, in seconds, which ones likely changed behavior your documentation hasn't caught up with yet. Free, no signup, no install required — just paste a repo URL and see your drift report.
Frequently asked questions
- What is documentation drift?
- Documentation drift is when your code changes but your README, API reference, or usage guides don't get updated to match — so the docs describe behavior that no longer exists. It happens quietly: a PR merges, nobody remembers to touch the docs, and the gap grows with every release.
- How does the checker decide a pull request is docs-relevant?
- It reads the actual code diff of each recent merged pull request and classifies whether the change affects documented behavior — new parameters, changed defaults, removed endpoints, that kind of thing. PRs that only touch comments, tests, lockfiles, or the docs themselves are filtered out automatically, since there's nothing for a doc fix to react to there.
- Does this tool read my private code or store it?
- It only works on public repositories, using the same pull request diffs anyone can already see on GitHub. Nothing is stored beyond a short-lived cache of the check result itself, so a repeat check on an unchanged repo doesn't re-run the same analysis.
- How do I actually fix the stale docs it finds?
- This free checker only reports drift — it doesn't open pull requests. Installing Verlio's GitHub App does the rest automatically: it watches your merged PRs going forward and opens a pull request with a drafted doc fix for you to review. It never merges anything itself.