← Saturday, September 26, 2026DatabasesTool

Safe-not-safe checks Postgres migrations with a browser-based parser

safenotsafe.dev Editor score 6/10

The tool uses libpg_query 17 compiled to WebAssembly in a browser worker, with a rule engine and no telemetry. It may help teams catch risky migration patterns, though the excerpt does not describe the rules or their coverage.

What
safe-not-safe is a browser-based tool for checking PostgreSQL migrations.
How
It downloads and compiles the libpg_query WASM parser in a browser worker to parse migration SQL.
Why it matters
Browser-side parsing gives engineers a way to inspect migrations and flag problems without relying on a remote parser.
SQL parse parse tree migration.sql browser worker libpg_query 17(wasm) rule engine
Migration SQL is parsed in the browser and passed to the rule engine for checking. Sketched from the article's own text.

Discussion

Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.

Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.

Your note

Private to you. Stored in this browser, and synced to your account when you are signed in.