Walk a SQLite database's real header, schema, B-trees, and pages — never modified, only read.
If you're here because something threw one of these, this tool shows you exactly what's wrong and how much is recoverable:
SQLite only — no Access/DBF/Berkeley DB/LevelDB/MySQL/Postgres/SQL Server/Oracle support yet (all real future engines, none built). No WAL or rollback-journal parsing yet, so a companion -wal/-journal file isn't read — only the main database file. No record carving from free or unallocated pages — recovered rows only ever come from a real, reachable B-tree leaf cell, never a guessed pattern match. No foreign-key cross-table validation, no FTS/RTree internals (virtual tables are detected from their SQL but not decoded), no per-page checksums (SQLite's base format doesn't have any). Row preview is capped to a table's first leaf page, not the whole table. Nothing is ever inferred — a column value is either decoded from real bytes or reported as unreadable, never guessed. This tool only inspects — it never writes, repairs, or rebuilds anything; that's a job for a future dedicated recovery tool.