Is your Postgres migration safe or not safe?

File EditSelectionViewCheck Help safe-not-safe — migration.sql offline ◆migration.sql✕ CHECKING ⌥⇧F⋯ session›migration.sql›0 statements 1 2 3 4 5 6 7 8 9 10 ALTER TABLE users ADD COLUMN status text DEFAULT 'active'; CREATE INDEX CONCURRENTLY users_created_at_idx ON users (created_at); ALTER TABLE orders ADD CONSTRAINT orders_user_id_fk FOREIGN KEY (user_id) REFERENCES users(id) NOT VALID; ALTER TABLE orders VALIDATE CONSTRAINT orders_user_id_fk; CHECKING Loading PostgreSQL parser. Downloading and compiling libpg_query WASM in a browser worker. 0 flagged of 0 PROBLEMSTERMINALOUTPUTPARSE TREERULE ENGINEbash+⌃` $ npx safe-not-safe check migration.sql parse libpg_query 17 (wasm) · initializing · 0 statements · 301 chars note Downloading and compiling the PostgreSQL WASM parser. No statements found. Paste a migration or load a sample. CHECKING — Loading PostgreSQL parser. Downloading and compiling libpg_query WASM in a browser worker. $ CHECKING0 flagged · 0 statementsLn 1, Col 1PostgreSQL 16SQLno telemetryGitHub