Python · SQLite · Offline reports

What changed in SQLite?
Check before you ship.

Review a migration or app update with read-only before/after snapshots. Compare schema and exact counts, spot increases in foreign-key violations and specified duplicate keys, and open one offline report.

View the sample audit Read the guide ☆ Star on GitHub

Synthetic data only. The demo opens directly; no installation needed.

Take a snapshot

Scan your database with explicitly selected candidate keys.

Repeat after an update

Use the same key rules so the snapshots cover comparable checks.

Compare and inspect

Open an offline HTML report, or use the regression exit code in CI.

Try the local workflow

git clone https://github.com/fuxing0910-hue/sqlite-audit-kit.git
cd sqlite-audit-kit
python -m sqlite_audit demo --output-dir demo

Python 3.10+ with sqlite3. Open demo/report.html after the command finishes. All example records are invented.

Download releases

How to audit SQLite before and after a migration

A read-only workflow for schema, NULLs, storage types, foreign keys and specified duplicate keys, with offline HTML/JSON output and an optional coding-agent skill.

Exact counts, stated limits

Scans are read-only and run in one snapshot transaction. Full scans can be expensive on large databases. Row-count changes, more NULLs and mixed storage types are observations; they do not automatically fail the regression gate.

Reports omit record payloads and duplicate-key values, but include schema SQL and diagnostic metadata. Review those before sharing your own report. The hosted demo contains synthetic fixtures only.