Audit any website from your terminal.

Rust runs the checks and reports. Node runs Lighthouse. Everything stays on your machine with no servers, no accounts, no telemetry.

$

auditkit — try it

Three commands

Run ak new once to open a workspace, then inspect and report. Everything runs in order, locally.

01

ak new Create a reusable client workspace under audits/.

02

ak inspect latest Run every check — HTML, security, and Lighthouse — for the newest workspace.

03

ak report latest Write the final report and client email, ready to send.

What gets audited

One pass covers structure, security, and performance then packages it into a report you can hand to a client.

html structure, metadata, and SEO checks
headers security header and policy inspection
lighthouse performance, a11y, best-practices, SEO
report client-ready markdown + email
save write results to any folder with --save
local runs on your machine with no servers, no accounts

Roadmap

Where Audit Kit is headed. Shipping now, queued next, then a set of focused doctors for the parts of a site that usually go wrong.

Now Audit Kit Foundation 5
- Local CLI workflow
- SEO / security / performance basics
- Markdown reports
- Lighthouse integration
- Agency-ready audit output
Next Better Website Signals 6
- More HTML / SEO checks
- Stronger security headers
- Cleaner report structure
- Config validation
- Clearer errors
- JSON output for automation
Then Network Doctor 6
- Capture network requests
- Detect slow endpoints
- Detect request loops
- Detect duplicate requests
- Flag heavy third-party scripts
- Summarize waterfall bottlenecks
Then Asset + Bundle Doctor 5
- Image optimization warnings
- JS / CSS weight checks
- Font loading checks
- Render-blocking resource checks
- Bundle cost summaries
Then Framework Doctor 5
- Detect React / Vue / Svelte / Solid
- Scan source repo when available
- Warn about render loops & effects
- Detect dependency-cycle mistakes
- Highlight suspicious client patterns