SELECT * FROM users WHERE id = 12345 AND name = 'Alice';
It treats SQL as code , not just as a string to ship over a wire. For platform engineers, DBREs, and backend developers who hate guessing games, stmtk is a breath of fresh air. stmtk tool
curl -sSL https://get.stmtk.dev | sh
We spend a lot of time talking about massive data pipelines, cloud warehouses, and complex ETL frameworks. But what about the humble SQL statement? The single SELECT , the 50-line UPDATE , or the terrifying MERGE that runs once a quarter? SELECT * FROM users WHERE id = 12345
stmtk analyze --dangerous vendor_script.sql stmtk scans for destructive patterns (unbounded DELETE , DROP TABLE , TRUNCATE inside transactions) and flags them. It won't stop you from shooting yourself in the foot, but it will tap you on the shoulder first. Why does your query cache have a 1% hit rate? Because every user sends a slightly different literal. stmtk normalize converts your specific query into a parameterized fingerprint. But what about the humble SQL statement
echo "SELECT * FROM orders WHERE total > 100" | stmtk analyze --dialect generic stmtk won't replace your database monitoring stack. It won't tune your work_mem for you. But it will fill the gap between "I typed a query" and "The query ran."