> parsing encoded files tends to introduce vulnerabilities If we are talking about binary formats, now there are systematic solutions like https://github.com/g

> parsing encoded files tends to introduce vulnerabilities If we are talking about binary formats, now there are systematic solutions like https://github.com/google/wuffs https://github.com/google/wuffs that protect against vulnerabilities. But SQLite is not just a format - it's an evolving ecosystem with constantly added features. And the most prominent issue was not even in core, it was in FTS3. What will SQLite add next? More json-related functions? Maybe BSON? It is useful, but does not help in this situation. Regarding traces, there are many forensics tools and even books about forensic analysis of SQLite databases. In well-designed format such tools should not exist in the first place. This is hard requirement: if it requires rewriting the whole file - then so be it.