How Docdrift works
Supported languages and frameworks
| Language | Frameworks | Status |
|---|---|---|
| TypeScript and JavaScript | Next.js, Express, Koa and Fastify, NestJS, Hono, Elysia, Hapi, AdonisJS, Vue and Nuxt, SvelteKit, Astro, Angular, React Router, React Router community routes, React Router (SPA), TanStack Router and Start, Qwik, SolidStart, Fresh, React Native, React Native Navigation, Expo Router, Electron, Socket.IO, tRPC, GraphQL, BullMQ, pg-boss, Inngest, Trigger.dev, node-cron, Netlify Functions, Cloudflare Workers, Firebase Functions, Vercel Functions, Supabase Edge Functions, Serverless Framework and AWS SAM, Convex, commander, yargs, oclif | Beta |
| Python | FastAPI, Flask, Django, Celery, Dramatiq, APScheduler, Click, Typer, argparse | Beta |
Beta: Docdrift runs every feature on it, but it hasn't passed our accuracy benchmark yet. If it failed the benchmark, its findings show up in the app and in the check details, not in pull request comments.
About the pull request comment
Docdrift opens one comment per pull request, only for high-confidence findings, capability warnings and change request criteria that weren't met, and updates that same comment. Once it's open, it can also list what the pull request says it did, marked as low confidence.
What Docdrift checks
- Your docs against your code: what your docs, rules and decisions say that the code doesn't do.
- Your capabilities: when a change removes or duplicates a page, route, job or command that already worked.
- Your change requests: whether each accepted criterion shows up in the code of the linked change.
Docdrift protects the pages, routes, jobs and other ways people use each capability. It doesn't notice when something inside a page stops working, like a button that saves straight to your database, or when a capability still exists but works differently.