squawkhq.com

What It Is

Squawk is a linter for PostgreSQL migrations with a core goal of “Prevent Downtime.” Before schema changes reach production, it detects issues that may cause read/write blocking, table rewrites, lock conflicts, or client incompatibilities. It can run as a CLI tool, and it can also be integrated into the development workflow through GitHub PR comments, GitHub Action, GitHub App, and a VSCode language server/extension.

Core Capabilities

In terms of rule coverage, Squawk is highly focused on safe online PostgreSQL migrations. It checks common modeling practices—such as avoiding character, preferring bigint, using timestamptz, and favoring identity columns—as well as high-risk DDL operations: concurrent index creation must not be run inside a transaction; indexes should be created/dropped with concurrent; validating foreign keys and NOT NULL constraints may block writes; and adding a column with a default value can trigger a table rewrite on older PostgreSQL versions. Its compatibility rules are also practical, including prohibitions against dropping databases/tables, dropping NOT NULL constraints, renaming tables or columns, and changing column types.

Integrations, API, and Documentation

Squawk provides a CLI and can publish results to GitHub Pull Requests via the upload-to-github subcommand. The official documentation includes GitHub Action workflow examples and also explains how to configure the GitHub App in non-GitHub Actions environments such as CircleCI, including App ID, Private Key, Install ID, and PR environment variables. VSCode support shifts checks earlier into the editor. The documentation quality is strong: rule pages typically include the problem, solution, links, and examples for SQL, Alembic, SQLAlchemy, golang-migrate, and related tools.

Pricing and Open-Source Information

The crawled content does not provide pricing, payment methods, commercial edition, or SLA information. Although the pages repeatedly point to the GitHub repository and sbdchd/squawk-action, they do not clearly display a license, so its open-source status cannot be concluded from the crawled text alone.

Pros, Cons, and Best-Fit Users

Its strengths are a clear focus, rules that closely match real PostgreSQL production migration pain points, and the ability to integrate into PRs, CI, and editors. Its limitations are that its scope is mainly PostgreSQL migration linting rather than a full database change management platform; GitHub App configuration is somewhat cumbersome; and commercial support information is limited. It is well suited to teams heavily using PostgreSQL, SaaS backend teams, DBA/platform engineering teams, and small to mid-sized engineering organizations that want to reduce migration-related downtime risk.

Access from China

The crawled content does not provide information about mainland China access, mirrors, or payment options. Because its integrations depend on the GitHub, GitHub Actions, and VSCode ecosystems, the network experience in China may be affected by GitHub availability. Actual usability should be verified with local network testing. Alternative or complementary tools include Atlas, Bytebase, Flyway, Liquibase, Sqitch, Prisma Migrate, and others.