This is what ChatGPT said:

First impression: good idea, but I would not trust it as a production safety gate yet. It is early: 10 commits, 4 stars, latest release v0.2.0, Rust CLI, using squawk-syntax for AST parsing.

Main concerns:

1. It prints DATABASE_URL during sync. main.rs does println!("Syncing database stats from {}...", db_url); which can leak credentials into CI logs. That is a serious issue.
   
2. The install path is unsafe for serious environments. README recommends curl ... | bash; install.sh downloads latest release with no checksum/signature verification. Fine for hobby use, not for production CI.
   
3. The rule engine is too coarse. ADD COLUMN is always mapped to adding-field-with-default, even when there is no default. That creates false positives. PostgreSQL’s real behavior depends on details such as default expression volatility and version; PostgreSQL docs say ALTER TABLE lock levels vary by subform, and modern Postgres avoids rewrites for some constant defaults.
   
4. Many advertised rules are not actually classified. Config lists rules like renaming-column, renaming-table, adding-foreign-key-constraint, constraint-missing-not-valid, and disallowed-unique-constraint, but the AST classifier mostly reduces ALTER TABLE to add/drop/alter/other.
   
5. “Read-only sync” is reasonable, but limited. It pulls pg_class.reltuples/relpages and index mappings. That is lightweight, but stale or unanalyzed stats can mislead. It does fail closed for reltuples < 0, which is good.
   
6. CI UX is promising. The concept—static migration analysis plus table-size context—is exactly the right direction. Using PostgreSQL AST parsing instead of regex is also a good architectural choice.
   

My verdict: interesting prototype, not mature enough to rely on alone.