Which local SQL checker helps review a small SQLite migration?

SQLFluff has the widest rules and the healthiest project of these, narrowly ahead of Sqruff and GoSQLX. None of these checkers proves SQLite will run your file, so run it on a copy too.

PRACTICAL PICKSPreferredPickOur Preferred PickLint and format with core rules$0

SQLFluff

Lints and formats a SQLite migration, reports SQL it cannot parse, and leaves such a file unchanged. It also reads ATTACH, VACUUM, REINDEX and ANALYZE.

Narrow lead over Sqruff (3.63 to 3.48) and GoSQLX (3.35). Run it with --rules core, and know that it rejects valid BEGIN IMMEDIATE.

Why SQLFluff is our Pick
PRACTICAL PICKSRisingStarOur Rising StarA newer Go linter and formatter$0

GoSQLX

A Go program first released in August 2025 that formats, lints and syntax-checks SQLite and fails with exit code 1 on SQL it cannot parse.

Its own pages disagree on how much SQLite it reads and say ATTACH, DETACH and VACUUM are not supported, and one maintainer stands behind it.

Why GoSQLX earned Rising Star

Who is this article for? Developers reviewing a short SQLite migration SQL file before testing it against a disposable database.

About 31 min read

What Preferred Pick, Rising Star and Ready to Rock mean

The quick list

Use these tools to tidy migration text and catch SQL they cannot read before review. Then run the file on a copy with SQLite itself, because each tool reads SQL with its own grammar.

All four are free and need no account, checked November 12, 2026. SQLFluff is MIT-licensed and needs Python 3.10 or later; GoSQLX is Apache-2.0 and installs with Go or a Visual Studio Code extension; Sqruff is Apache-2.0 and ships as one program; the Prettier SQL-CST plugin is GPL-3.0-or-later and needs Node.js and Prettier. None of them backs up a database or runs a migration.

The comparison at a glance

Compare which SQLite statements each tool can read, what happens to SQL it cannot read, what its default fix changes, and what it takes to install.

Order follows our verdict for checking a short SQLite migration before review, not speed or popularity. All tools remain selectable.

Tools for formatting and checking SQLite migration SQL before review
FeatureSQLFluffSqruffGoSQLXPrettier plugin SQL-CST
Best fitLinting and formatting with the widest rules and CI output of the linters; run with --rules coreThe same kind of check from one self-contained program, with no PythonA Go linter and formatter that also checks syntax; first released in August 2025; its own pages disagree on SQLite support (“Keywords + basic parsing” in one table, 348 statements passing in another)Formatting only, with the widest SQLite grammar, in a project that already uses Prettier
What it checksLint rules, formatting fixes and a parse-tree viewLint rules and formatting fixesLint rules, formatting fixes, a syntax check, a syntax-tree view and a security scannerFormatting only; no lint rules
Cost and licence (November 12, 2026)Free; MIT licence; no accountFree; Apache-2.0 licence; no accountFree; Apache-2.0 licence; no accountFree; GPL-3.0-or-later (parser GPL-2.0-or-later); no account
SQLite transactionsReads BEGIN, COMMIT and ROLLBACK; not BEGIN IMMEDIATE, EXCLUSIVE or DEFERRED, SAVEPOINT or RELEASESame gap as SQLFluff; 0.44.0 added no transaction syntaxChecks transaction statements against each dialect’s grammar; does not say whether BEGIN IMMEDIATE or savepoints are readReads all of these
SQL it cannot parseLint reports a parse error and fails; fix leaves the file unchangedAdd --parsing-errors to lint, which otherwise passes SQL it cannot parse (an open report, November 1, 2026); fix leaves the file unchangedLint and validate report a syntax error and exit 1; its guide does not say what format does with a file it cannot parseStops with a syntax error; nothing is formatted
What the default fix changesEvery rule runs unless you choose --rules core; some rules restructure SQLCore rules onlyKeywords are uppercased by default; comments are kept; lint can fix some violationsLayout, plus keyword rewrites such as AS in aliases and != for <>; can be turned off
Open reports (November 12, 2026)ST01 deletes a comment in ELSE NULL (not a core rule); the AL05 and ST06 reports were fixed in 4.5.0Valid SQLite rejected: COLLATE after an expression, INDEXED BY, before and after as column names; the AM02 fix can write UNION DISTINCT, which SQLite rejectsIts open issue reports were not read; GitHub lists no published security advisoryComments moved or reordered (open since 2023); the CROSS JOIN … ON rejection was fixed on October 30, 2026
InstallPython 3.10+ package, or DockerOne release binary, Homebrew, pip, cargo or Dockergo install, a Visual Studio Code extension that bundles the program, or a GitHub ActionNode.js with Prettier and the plugin
Reader reviewsNo reviews yet. Write a reviewNo reviews yet. Write a reviewNo reviews yet. Write a reviewNo reviews yet. Write a review

SQLFluff, GoSQLX and Sqruff lint and format; the Prettier plugin only formats. None of them proves SQLite will run your file, so run it on a copy of your database first. Our lead for SQLFluff is narrow. Earlier check record, October 3, 2026.

All features and sources 13 criteria

Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.

SQLite grammar and unreadable SQL

Show 5 criteria
SQLite grammar and unreadable SQL
FeatureSQLFluffSqruffGoSQLXPrettier plugin SQL-CST
SQLite transactionsReads BEGIN, COMMIT and ROLLBACK; not BEGIN IMMEDIATE, EXCLUSIVE or DEFERRED, SAVEPOINT or RELEASESame gap as SQLFluff; 0.44.0 added no transaction syntaxChecks transaction statements against each dialect’s grammar; does not say whether BEGIN IMMEDIATE or savepoints are readReads all of these
ATTACH, VACUUM, REINDEX, ANALYZERead since 4.4.0 (October 2, 2026)Read since 0.44.0 (October 30, 2026)ATTACH and DETACH are not parsed and VACUUM is not supported, by its own compatibility page; REINDEX and ANALYZE not statedRead
SQLite 3.53 ALTER COLUMN … NOT NULLNot readNot readNot statedNot read
SQL it cannot parseLint reports a parse error and fails; fix leaves the file unchangedAdd --parsing-errors to lint, which otherwise passes SQL it cannot parse (an open report, November 1, 2026); fix leaves the file unchangedLint and validate report a syntax error and exit 1; its guide does not say what format does with a file it cannot parseStops with a syntax error; nothing is formatted
Files over 20,000 bytesSkipped by default without failing; set large_file_skip_failSkipped by default without failing; set large_file_skip_failNot statedNo size skip among the plugin’s documented options
Sources for sqlite grammar and unreadable sql

From each project’s published grammar source code and default configuration, checked October 20, 2026 (SQLFluff 4.4.0, Sqruff 0.41.0, sql-parser-cst 0.42.3), and release notes and open reports read November 12, 2026 (SQLFluff 4.5.0, Sqruff 0.44.0), and GoSQLX’s compatibility page and command guide read November 12, 2026 (version 1.17.0). A grammar is the tool’s reading of SQL, not SQLite’s; run the file on a copy with sqlite3 -bail to know whether SQLite accepts it. SQLite transaction syntax.

Fixes and review

Show 4 criteria
Fixes and review
FeatureSQLFluffSqruffGoSQLXPrettier plugin SQL-CST
What it checksLint rules, formatting fixes and a parse-tree viewLint rules and formatting fixesLint rules, formatting fixes, a syntax check, a syntax-tree view and a security scannerFormatting only; no lint rules
What the default fix changesEvery rule runs unless you choose --rules core; some rules restructure SQLCore rules onlyKeywords are uppercased by default; comments are kept; lint can fix some violationsLayout, plus keyword rewrites such as AS in aliases and != for <>; can be turned off
Open reports (November 12, 2026)ST01 deletes a comment in ELSE NULL (not a core rule); the AL05 and ST06 reports were fixed in 4.5.0Valid SQLite rejected: COLLATE after an expression, INDEXED BY, before and after as column names; the AM02 fix can write UNION DISTINCT, which SQLite rejectsIts open issue reports were not read; GitHub lists no published security advisoryComments moved or reordered (open since 2023); the CROSS JOIN … ON rejection was fixed on October 30, 2026
Review and CI outputparse command; GitHub, GitLab and SARIF outputJSON, SARIF and GitHub annotation output; language server for editorslint, validate, format --check and parse commands; text, JSON and SARIF output; language serverprettier --check lists files that need formatting
Sources for fixes and review

From documentation and default configuration checked October 20, 2026, and open issue reports and release notes read November 12, 2026. Issue reports describe what users ran into, not how often it happens. Read every formatting diff before committing it.

Setup, cost and upkeep

Show 4 criteria
Setup, cost and upkeep
FeatureSQLFluffSqruffGoSQLXPrettier plugin SQL-CST
InstallPython 3.10+ package, or DockerOne release binary, Homebrew, pip, cargo or Dockergo install, a Visual Studio Code extension that bundles the program, or a GitHub ActionNode.js with Prettier and the plugin
Cost and licence (November 12, 2026)Free; MIT licence; no accountFree; Apache-2.0 licence; no accountFree; Apache-2.0 licence; no accountFree; GPL-3.0-or-later (parser GPL-2.0-or-later); no account
Latest release (checked November 12, 2026)4.5.0, October 30, 20260.44.0, October 30, 20261.17.0, October 31, 20260.25.1, November 5, 2026
Who maintains itOpen-source project with many contributors; three advisories, all fixed by 4.2.0; a security policy pageNearly all recent changes by one developer; maker Quary was acquired in January 2025 and its website no longer loads; no security policyOne named maintainer and ten listed contributors, one of them Claude; first release August 2025; a security policy; no organisation behind itOne developer; pre-1.0; style “still very much subject to change”
Sources for setup, cost and upkeep

From each project’s repository and release records, checked November 12, 2026, and, from October 20, 2026, package records and, for Sqruff, the Tobiko Data and Fivetran acquisition announcements.

What matters when choosing

SQLFluff is our Preferred Pick for formatting and linting a short SQLite migration file before someone reviews it. Run it as sqlfluff lint --dialect sqlite --rules core and sqlfluff fix --dialect sqlite --rules core, or set dialect = sqlite and rules = core in a .sqlfluff file. Since version 4.4.0 (October 2, 2026) it reads ATTACH, DETACH, VACUUM, REINDEX and ANALYZE, as Sqruff now does since 0.44.0, and it has fewer open reports of valid SQLite that it rejects. It reports SQL it cannot parse as an error, and fix leaves such a file unchanged by default. It has the widest set of rules, a parse command that shows how it read your file, and output for GitHub, GitLab and SARIF code scanning. It is free, MIT-licensed and developed by a large group of contributors. SQLFluff, 4.5.0 release, command reference

Our lead is narrow. On weights we fixed before scoring, SQLFluff scored 3.63 out of 5, Sqruff 3.48, GoSQLX 3.35 and the Prettier SQL-CST plugin 3.33. The weights favour SQLite grammar coverage and safe fixes, and SQLFluff wins because it has many active contributors, its rules and CI output are wider than GoSQLX’s or Sqruff’s, it is easier to set up than GoSQLX, which has one maintainer, and Sqruff has more open reports of valid SQLite it rejects. All four are free, so price does not separate them. Sqruff comes out ahead if a single self-contained program matters more to you than the project’s long-term health. The Prettier plugin comes out ahead if you want only formatting, not lint rules.

Use --rules core, because SQLFluff’s default runs every rule, and some of them rewrite SQL rather than only tidying it. One of them, ST01, deletes a comment written inside a redundant ELSE NULL branch of a CASE expression. That report was still open on November 12, 2026, with a proposed fix not yet merged. Two reports opened on October 19 described other automatic fixes that break a query or change its results: AL05, one of the core rules, and ST06, which is not one. The AL05 report was closed on October 20, and the 4.5.0 release notes (October 30) list a fix for ST06’s case and fixes to AL05’s false positives. Both concerned queries rather than typical schema changes. Whatever settings you use, read the diff before you commit a fix. ST01 report, AL05 report, ST06 report, 4.5.0 release, rule groups

None of these tools proves that SQLite will run your file. Each reads SQL with its own grammar, not SQLite’s. SQLFluff and Sqruff cannot read BEGIN IMMEDIATE, BEGIN EXCLUSIVE or BEGIN DEFERRED, which are valid SQLite; their October 30, 2026 releases list no change to transactions. SQLFluff, Sqruff and the Prettier plugin do not read the ALTER TABLE … ALTER COLUMN … SET NOT NULL form that SQLite added in version 3.53.0 (April 2026), and GoSQLX does not say whether it does. No linter catches mistakes that only SQLite can see, such as adding a NOT NULL column without a default, or switching foreign keys off inside a transaction, where SQLite ignores the setting. Run the file on a copy of your database with SQLite’s own command-line program, for example sqlite3 -bail copy.db < migration.sql, which stops at the first error. Then use your migration tool. SQLite transactions, ALTER COLUMN in 3.53.0, ADD COLUMN rules, PRAGMA foreign_keys, sqlite3 command-line program

GoSQLX is our Rising Star: a newer linter and formatter in one Go program. It parses, formats, lints and syntax-checks SQL for eight dialects, SQLite among them, and its first release, version 1.0.0 on August 23, 2025, is within our two-year window for newer tools. Version 1.17.0 came out on October 31, 2026 under the Apache-2.0 licence. Run gosqlx validate --dialect sqlite and gosqlx lint --dialect sqlite (the default dialect is PostgreSQL); both exit 1 when SQL does not parse, and gosqlx format --check exits 1 when a file needs formatting, so each works as a CI gate. Its own compatibility page lists a SQLite dialect checked against 348 statements, and PRAGMA and WITHOUT ROWID as fully parsed, but also says ATTACH and DETACH are not parsed and VACUUM is not supported. We could not find whether it reads BEGIN IMMEDIATE or savepoints, or what format does with a file it cannot parse, so test both before relying on it. One named developer owns it, with ten listed contributors, and GitHub lists a security policy and no published security advisory. GoSQLX, compatibility page, command guide, releases, security advisories

Disclosure: Practical Picks is researched and written with Claude, an AI model made by Anthropic. GoSQLX advertises a Claude Code plugin and an MCP server for AI agents. AI features carried no weight in this comparison, and we have no relationship with GoSQLX or Anthropic.

Sqruff, which we named our Rising Star in October, is a Rust linter and formatter that started as a reimplementation of SQLFluff and copies SQLFluff’s grammar changes, its rule names and much of its configuration. It was first released in February 2024: its first release is dated February 23, 2024 in our October review, and a Hacker News post announcing it is dated February 12, 2024. That is before November 12, 2024, the start of our two-year window for newer tools, so it no longer qualifies for the label. It remains a close check. By default it runs only the core rules and does not fix a file it cannot parse. Add --parsing-errors to every sqruff lint command: an open report from November 1, 2026 shows lint passing a file that sqruff fix and sqruff parse flag as unparsable. Version 0.44.0 (October 30, 2026) added ATTACH, DETACH, VACUUM, REINDEX and ANALYZE, so its grammar now matches SQLFluff’s on those statements. It still cannot read the BEGIN variants above, and open reports from November 2026 describe valid SQLite it rejects: COLLATE after an expression, INDEXED BY, and before or after as column names. Another open report says its AM02 fix writes UNION DISTINCT, which SQLite rejects; we could not confirm whether AM02 runs by default. Its future is also less clear. The company that made it, Quary, was bought by Tobiko Data in January 2025, and Tobiko was bought by Fivetran in September 2025. Neither announcement mentions Sqruff. On October 20, 2026, quary.dev did not load. One developer is credited with nearly every change in its recent releases. Sqruff, 0.44.0 release, lint report, COLLATE and INDEXED BY report, AM02 report, Hacker News post, February 12, 2024, Tobiko’s announcement, Fivetran’s announcement

Consider the Prettier SQL-CST plugin if you want formatting only, in a JavaScript project. It is a plugin for the Prettier code formatter, made by the maintainer of the older SQL Formatter library, who now recommends it instead. Its parser has its own grammar for SQLite, which its maker describes as full support for SQLite 3.45. In the published source code on October 20, 2026, that grammar reads BEGIN IMMEDIATE, savepoints, STRICT tables and the maintenance statements. It has no lint rules: prettier --check tells you only whether the file is already formatted, or stops with a syntax error. Know two limits before you rely on it. A report open since October 2023 says formatting can move and reorder comments. And the plugin is pre-1.0, maintained by one developer, and its maker says the formatting style is “still very much subject to change”, so pin its version. Prettier plugin SQL-CST, comment report, CROSS JOIN report

All four run on your own computer, cost nothing and need no account. Keep migration files in version control, so a formatting change is a diff you can read and undo. This comparison does not rank speed.

SQLFluff

Preferred Pick · lint and format, core rules only

$0MIT-licensed Python package, no account

Choose SQLFluff to format and lint a short SQLite migration before review. Run it with --dialect sqlite --rules core and read the diff. Our lead is narrow.

Reasons to choose it

  • Reports SQL it cannot parse; fix leaves such a file unchanged
  • Widest rule set, a parse command, and GitHub, GitLab and SARIF output
  • Many contributors, a security policy page and a release at the end of October 2026

What to watch

  • Rejects valid BEGIN IMMEDIATE, EXCLUSIVE and DEFERRED, and savepoints
  • Default runs every rule; open report of ST01 deleting a comment
  • Needs Python 3.10 or later, or Docker

SQLFluff is an open-source SQL linter and formatter written in Python. It has been developed since 2018 in the sqlfluff GitHub organization. sqlfluff lint reports problems, sqlfluff fix corrects the ones it can, and sqlfluff parse prints the syntax tree it built from your file. That tree is SQLFluff’s reading of the SQL, not SQLite’s. Version 4.5.0 came out on October 30, 2026 (4.4.0 on October 2), needs Python 3.10 or later and is MIT-licensed. Install it with pip or use the project’s Docker image; the project also lists a Visual Studio Code extension. Output formats include GitHub annotations, SARIF and, since 4.4.0, GitLab Code Quality. Repository, package record, 4.5.0 release, command reference

On SQLite, its grammar is good but not complete. The project’s own README says it supports its dialects “though perhaps not in full”. In the 4.4.0 source code, the SQLite dialect covers tables, including STRICT and WITHOUT ROWID, indexes, views, triggers, PRAGMA, and since 4.4.0 also ATTACH, DETACH, VACUUM, REINDEX and ANALYZE. Its transaction grammar accepts BEGIN, COMMIT, ROLLBACK and END, optionally followed by TRANSACTION. It does not accept BEGIN IMMEDIATE, EXCLUSIVE or DEFERRED, or SAVEPOINT and RELEASE, all of which SQLite documents. A migration that starts with BEGIN IMMEDIATE; will fail lint even though SQLite runs it. Its ALTER TABLE grammar covers renaming and adding or dropping columns, but not SQLite 3.53’s ALTER COLUMN. The 4.5.0 release notes list further SQLite fixes (identifiers such as MATCH and VIRTUAL, bare functions, underscores in numbers) and no transaction change. SQLite dialect source, SQLite transaction syntax

Read the full SQLFluff analysis and sources

Two defaults matter for a migration check. First, SQLFluff runs every rule unless you restrict it. The core group is a smaller set the project considers broadly applicable, and it leaves out ST01, the rule with the open comment-deletion report. Second, both SQLFluff and Sqruff skip files larger than 20,000 bytes by default without failing the run. A long migration could therefore pass unchecked. Set large_file_skip_fail = True, or raise the limit, if your files can be that large. fix does not change a file it cannot parse unless you set fix_even_unparsable. Default configuration, rule groups

GitHub lists three security advisories for SQLFluff. Two from May 2026 concern deliberately deep or large SQL exhausting the parser, and were fixed in 4.1.0 and 4.2.0. One from 2023 concerns a library_path setting in an untrusted configuration file. Version 4.5.0 includes all three fixes, and --library-path none turns the setting off if you lint a repository you do not trust. By November 12, 2026 its GitHub security page linked a security policy, which it had not on October 20. The 4.5.0 notes credit fifty-five first-time contributors, and the repository had about 10,000 GitHub stars. Recursion advisory, node-limit advisory, configuration advisory, security page

In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, SQLFluff 4.4.0 formatted a small synthetic SQLite script and left it unchanged on a second run. It rejected a copy with a missing bracket and did not change that file. Its default fix removed a comment from an ELSE NULL branch, which --rules core kept. It also rejected a valid BEGIN IMMEDIATE script that SQLite ran. These observations match the source code and the open report described above. They did not decide the Pick. Earlier check record, October 3, 2026

Used SQLFluff? Share your experience to help other readers choose.

Sqruff

Also close · one binary, no Python

$0Apache-2.0 release binary, no account

Consider Sqruff if you want the same kind of check from one self-contained program. Add --parsing-errors to lint, and expect a few valid SQLite statements to fail.

Reasons to choose it

  • One release binary, Homebrew, pip, cargo or Docker
  • Core rules by default; fix leaves an unparsable file unchanged
  • Follows SQLFluff’s grammar changes and rule codes, now including ATTACH, VACUUM and REINDEX

What to watch

  • Lint reports parse errors only with --parsing-errors
  • No BEGIN IMMEDIATE or savepoints; open reports of valid SQLite it rejects
  • Maker acquired in 2025; nearly all recent changes by one developer

Sqruff is a SQL linter and formatter written in Rust and published in the quarylabs GitHub organization. Its documentation says it “started as an exact replacement for SQLFluff but is diverging”. It still copies SQLFluff’s grammar changes and uses the same rule codes. Version 0.44.0 came out on October 30, 2026, and Sqruff is Apache-2.0 licensed. Install it with Homebrew, pip, cargo or a release binary for Linux, macOS or Windows. The project also offers a Docker image, a GitHub Action, a Visual Studio Code extension and an editor language server (sqruff lsp). Output formats include JSON, SARIF and GitHub annotations. Repository, 0.44.0 release, installation, command reference

Its defaults suit a migration check. It runs only the core rules unless you ask for more, so ST01 does not run. It also does not fix a file it cannot parse. The catch is lint: in the source code on October 20, 2026, fix always collects parse errors, but lint does so only when you add --parsing-errors. Use sqruff --dialect sqlite --parsing-errors lint in any check that should fail on unreadable SQL; a report opened on November 1, 2026 shows that without the flag lint passes a file sqruff fix and sqruff parse flag as unparsable. Like SQLFluff, it skips files over 20,000 bytes by default without failing. Its documentation now describes a parse command for viewing the syntax tree. In our earlier October 3 check, the 0.40.0 release program did not list one, but a user’s report from November 2026 runs sqruff parse on the 0.44.0 package from PyPI, so that build has it; we did not confirm it for the other release programs. Default configuration, parse-error handling in source, lint and parse documentation

Read the full Sqruff analysis and sources

Its SQLite grammar is close to SQLFluff’s but has more open problems. The 0.41.0 source had the same transaction gap: BEGIN with IMMEDIATE, EXCLUSIVE or DEFERRED, SAVEPOINT and RELEASE are not read, and the 0.44.0 notes list no transaction change. Its 0.44.0 notes add ATTACH, DETACH, VACUUM, REINDEX and ANALYZE, which SQLFluff added in 4.4.0. Recent releases fixed several SQLite problems that users reported. Version 0.40.0 (August 14, 2026) added STRICT tables, fixed trigger parsing, and added column-level ON CONFLICT clauses, which the formatter had “lost or mangled” before. Earlier, version 0.29.3 inserted a space into SQLite blob literals such as X'1234', which breaks them. That was fixed in December 2025. On October 20, 2026 GitHub showed no open Sqruff issue mentioning SQLite; on November 12 it showed four. Two report valid SQLite rejected by the parser (a COLLATE after an expression and INDEXED BY, and before or after as column names), one is the lint report above, and one says the AM02 fix writes UNION DISTINCT, which SQLite rejects. SQLite dialect source, ON CONFLICT report, blob literal report, open reports

The bigger question is who stands behind it. The README still carries a “Made by Quary” badge linking to quary.dev. On October 20, 2026 that address returned a “deployment could not be found” page, and the certificate for www.quary.dev had expired on February 22, 2026. Sqruff’s documentation, on a quary.dev subdomain, still loaded. Tobiko Data announced on January 15, 2025 that it had acquired Quary, without mentioning Sqruff. Fivetran announced on September 3, 2025 that it had acquired Tobiko Data, also without mentioning Sqruff. In the UK, Quary Technology Limited, whose directors included Quary’s founder, applied to be struck off the companies register in May 2025 and was dissolved on July 29, 2025. Releases have continued: 0.38.0 to 0.44.0 came out between April and October 30, 2026. But nearly every change in them is credited to one developer, and on November 12, 2026 GitHub detected no security policy for the project. It listed no security advisory for Sqruff on October 20 or November 12. As rough signals of use, it had about 1,400 GitHub stars and about 153,000 downloads from PyPI in the previous month. Release history, Tobiko’s announcement, Fivetran’s announcement

In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, Sqruff 0.40.0 behaved like SQLFluff on the same small synthetic files. It fixed the spacing, rejected the copy with a missing bracket without changing it, and rejected the valid BEGIN IMMEDIATE script. Its default fix kept the ELSE NULL comment. That check ran lint with --parsing-errors. These observations match the source code; they did not decide its ranking. Earlier check record, October 3, 2026

Used Sqruff? Share your experience to help other readers choose.

GoSQLX

Rising Star · a newcomer worth considering

$0Apache-2.0 Go program, no account

Why Rising Star? First released in August 2025, GoSQLX is the only tool here from the last two years that reads SQLite with its own dialect, checks syntax with a failing exit code, formats and lints, and it is the only qualifying tool. Its documented gaps in SQLite maintenance statements, the unanswered questions about transactions and unreadable files, and its single maintainer are the limits. This is not our broader Ready to Rock endorsement.

Consider GoSQLX if you want a single Go tool that formats, lints and syntax-checks SQLite and will accept a newer, less proven project. Run validate and lint with --dialect sqlite in CI and read every formatting diff.

Reasons to choose it

  • Lint and validate exit 1 on a syntax error
  • Format check, lint rules, a syntax-tree view, JSON and SARIF output, and a language server
  • First released in August 2025 and releasing often; no published security advisory

What to watch

  • Its own compatibility page says ATTACH, DETACH and VACUUM are not supported
  • Does not say whether BEGIN IMMEDIATE or savepoints are read, or what format does with a file it cannot parse
  • Installed with go install or a Visual Studio Code extension; one named maintainer

GoSQLX is a pure-Go SQL parser, formatter, linter and security scanner, published by the developer ajitpratap0 on GitHub under the Apache-2.0 licence. Its commands include validate, format, lint, parse (the syntax tree), analyze and a language server. Install it with go install, through a Visual Studio Code extension that bundles the program, or with its GitHub Action. Output formats include text, JSON and SARIF. Its first release was version 1.0.0 on August 23, 2025, and version 1.17.0 followed on October 31, 2026, with 29 releases in total. Repository, command guide, releases

For a migration check, its useful behaviour is the exit codes. Its guide says lint exits 1 on any violation or on SQL that does not tokenize or parse, format --check exits 1 when a file needs formatting, and validate reports invalid SQL. Formatting keeps comments, and its guide says keywords are uppercased by default. The guide does not say what format does with a file it cannot parse, so run it only after validate passes. Run gosqlx validate --dialect sqlite and gosqlx lint --dialect sqlite, because the default dialect is PostgreSQL; both exit 1 when SQL does not parse. Command guide

Read the full GoSQLX analysis and sources

On SQLite, its compatibility page lists the dialect as checked against 348 statements with no failures, and PRAGMA and WITHOUT ROWID as fully parsed. The same page lists limits: ATTACH and DETACH are not parsed, VACUUM is not supported and virtual tables are not supported. It says transaction statements are checked against each dialect’s grammar, but does not say whether BEGIN IMMEDIATE or savepoints are read, and we did not find a statement about REINDEX, ANALYZE, STRICT tables or SQLite 3.53’s ALTER COLUMN. Treat those as untested for your files. Compatibility page

On November 12, 2026 GitHub showed no published security advisory and a security policy, about 124 stars, 29 releases and ten listed contributors, one of them Claude; the repository belongs to one named developer, and we found no company behind it. We did not read its open issue reports. Its commit history describes test runs on Windows, macOS and Linux. Security advisories, repository

Used GoSQLX? Share your experience to help other readers choose.

Prettier plugin SQL-CST

Also consider · formatting only, widest SQLite grammar

$0GPL-licensed npm package, no account

Choose the Prettier SQL-CST plugin if you want consistent formatting rather than lint rules, your project already uses Prettier, and your migrations use SQLite statements the linters reject. Pin its version.

Reasons to choose it

  • Reads BEGIN IMMEDIATE, savepoints, STRICT tables, ATTACH and VACUUM
  • Stops with a syntax error instead of formatting SQL it cannot read
  • Fits an existing Prettier setup and editor integration

What to watch

  • No lint rules; it checks formatting only
  • Open report of comments being moved or reordered
  • Pre-1.0 and one developer; its parser has an open report about SQLite reserved words

The Prettier SQL-CST plugin (prettier-plugin-sql-cst) adds SQL to Prettier, the code formatter widely used in JavaScript projects. Run it with prettier --plugin prettier-plugin-sql-cst --parser sqlite, or set it up in a Prettier configuration file. By default it treats .sql files as SQLite. Its maker also maintains the older SQL Formatter library. That library’s README says it is in maintenance mode and recommends this plugin, which it says “already has full support for SQLite and BigQuery syntax”. Version 0.25.1 came out on November 5, 2026, with its parser, sql-parser-cst, at 0.44.1. The grammar details below were read in parser 0.42.3’s published source on October 20, 2026. The plugin is GPL-3.0-or-later and the parser GPL-2.0-or-later; those terms govern distributing the tools, not the SQL they format. Plugin README, parser README, SQL Formatter README

Its advantage is the grammar. The parser’s README describes full support for SQLite 3.45. In its published grammar on October 20, 2026, the SQLite rules include BEGIN DEFERRED, IMMEDIATE and EXCLUSIVE, SAVEPOINT and RELEASE, STRICT and WITHOUT ROWID tables, ATTACH, DETACH, VACUUM and PRAGMA. A file the parser cannot read stops with a syntax error that gives a line and column. Prettier’s documentation gives exit code 2 for errors, as distinct from 1 for files that need formatting. The gaps: it does not read SQLite 3.53’s ALTER COLUMN, and an open parser report asks for SQLite’s reserved keywords to be determined properly. A regression that made the parser reject CROSS JOIN … ON and CROSS JOIN … USING, which SQLite accepts, was reported on October 13, 2026 and fixed on October 30. Parser grammar, CROSS JOIN report, Prettier exit codes

Read the full Prettier plugin SQL-CST analysis and sources

It is a formatter, not a linter. It checks only that a file is formatted the way it would format it, with no rules about aliases, ambiguous columns or naming. Its default sqlCanonicalSyntax setting rewrites some syntax as well as layout. It adds AS to aliases, changes <> to !=, INSERT to INSERT INTO, DELETE to DELETE FROM and CREATE TEMP TABLE to CREATE TEMPORARY TABLE. These rewrites do not change what SQLite does, and you can turn them off. A more serious open report, from October 2023 and written about BigQuery SQL, shows formatting moving comments and merging two line comments onto one line in reverse order. The maintainer called this “a much more serious issue” and said the cause may lie in Prettier’s own comment handling. You also need Node.js and Prettier, one developer maintains both packages, and the maker says the style is “still very much subject to change”. The repository had about 200 GitHub stars, and npm counted about 182,000 downloads of the plugin in the previous month. Style guide and canonical syntax, comment report, npm package

The plugin was not part of our earlier October 3 check.

Used Prettier plugin SQL-CST? Share your experience to help other readers choose.

Which product are we missing?

Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.

Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.

Suggest a product

Opens an email draft with this article attached as a link. Nothing is sent until you send it.

No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.

What people are saying

Practical Picks has no reader reviews for these tools yet. Issue trackers show what users run into, not how often it happens. For SQLFluff, the open report on November 12, 2026 is the ST01 comment deletion (September 22, 2026), with a proposed fix not yet merged; the two reports filed on October 19 about AL05 and ST06 fixes that break queries were resolved, the AL05 one on October 20 and the ST06 one in the 4.5.0 release. Sqruff’s earlier SQLite reports from users, including the lost ON CONFLICT clauses and the broken blob literals, were closed with fixes, but four new SQLite-related reports were open on November 12, listed above. For GoSQLX we did not read the open issue reports. For the Prettier plugin, the comment-reordering report has been open since 2023, and the CROSS JOIN regression reported in October was fixed on October 30. SQLFluff ST01 report, AL05 report, ST06 report, Sqruff ON CONFLICT report, Prettier plugin comment report, CROSS JOIN report

As rough signals of use, on October 20, 2026: SQLFluff had about 10,000 GitHub stars and 9.4 million PyPI downloads in the previous month; GoSQLX about 124 stars (November 12, 2026); Sqruff about 1,400 stars and 153,000 PyPI downloads; and the Prettier plugin about 200 stars and 182,000 npm downloads. Homebrew counted about 7,900 installs of SQLFluff and 2,500 of Sqruff in the previous year. Download counts include automated builds and are not counts of users.

How we researched

This is public-source research. For this review we did not install or run any tool, create accounts or contact a maker. No maker supplied access or payment, and our links carry no affiliate tracking. We first compared SQLFluff and Sqruff on October 3, 2026, including a small hands-on check described below. On October 20, 2026 we rechecked documentation, release records, published source code, issue trackers, GitHub and OSV security advisories, licences and package records. We also checked the status of the company that made Sqruff, added a candidate we had missed, and made the decision again from public evidence. On November 12, 2026 we read the four projects’ release notes, repository pages and open reports, confirmed that all four cost nothing, and searched again for tools first released in the last two years.

We wrote this for a developer who wants to check a short SQLite migration file on their own computer before a colleague reviews it and before running it on a copy of the database. The job is consistent formatting, a clear failure on SQL the tool cannot read, no changes to a file it cannot read, and a diff a person can review. Every option had to run locally on .sql files from a command line, read SQLite with its own grammar, and stop with an error on SQL it cannot parse. Before scoring, we fixed five criteria and their weights: SQLite grammar coverage (30%), safe fixes that keep meaning and comments (25%), review value beyond layout, such as lint rules and parse output (15%), setup and fit for a CI check (15%), and project health, licence and cost (15%). Because all four are free, each scores the same on the cost part of the last criterion, which therefore adds the same amount to every total whatever price weight a reader prefers. SQLFluff scored 3.63, GoSQLX 3.50, Sqruff 3.48 and the Prettier plugin 3.33. Sqruff comes out ahead if setup counts for 25% and project health for 5%. The Prettier plugin comes out ahead if lint rules count for nothing and grammar for 45%. Those are the conditions in our assessment.

We checked that every widely used option for this job was either compared or set aside for a stated reason. SQLite’s own sqlite3 program is the only check that knows SQLite’s grammar for certain, and it also catches errors no text checker sees. But it checks validity by running the file, it does not format or lint, and EXPLAIN compiles one statement at a time against the current schema without applying earlier ones. So we recommend it alongside these tools rather than instead of them. We set aside SQL Formatter (a formatter in maintenance mode whose maker recommends the plugin above) and prettier-plugin-sql (it wraps SQL Formatter or node-sql-parser). We set aside sqlfmt (its README says it is not a linter, does not build a syntax tree and formats only select, delete, grant, revoke and create function statements). We also set aside Squawk (a migration linter for PostgreSQL only) and sqlcheck (no release since March 2022). The editor language servers sqls and sql-language-server are built mainly for editing. sqls offers completion and formatting inside an editor, and GitHub published a command-injection advisory for one sqls version in October 2025. sql-language-server bundles a small linter, sqlint, but neither package has had a release since November 2024. We set aside SQLGlot, a SQL library whose README says it “is a transpiler, not a validator”, and Atlas’s migrate lint, which checks migrations for destructive changes but does not format or lint SQL text (it has also needed a paid Atlas Pro account since version 0.38). Our separate SQLite schema-change comparison covers Atlas. We also searched Hacker News, PyPI, npm, GitHub and recent tool roundups for newcomers. In October, the new tools we found were a static analyzer for security and performance problems that does not format, with conflicting licence information and no commits since June 2026, and a formatter with no SQLite mode. Neither met our Rising Star threshold.

For the newcomer label we looked at tools first released on or after November 12, 2024, using Hacker News searches, GitHub topic listings for SQL linters and SQL formatters, and our October search. Sqruff (February 2024) and the Prettier plugin (npm, January 2023) are older than that. GoSQLX qualified: first release August 23, 2025, available now, described as tested on Windows, macOS and Linux runners, shown to check SQLite syntax and exit 1 on errors, and with no published security advisory. Scythe, a Rust tool that generates code from SQL, formats and lints through Sqruff’s engine, which dates from February 2024, so for this job it is Sqruff under another name and may share Sqruff’s gap in reporting unparsable SQL; its earliest release we could not date. sqlike checks queries rather than formatting migration files, and its analysis engine is a closed service that runs on a remote server. sqlriver (formerly Holywell) formats but does not read SQLite on its own, and a blog post about another new formatter, sqlfmt by Dimitri Fontaine, did not load, so we did not assess it. GoSQLX is the only qualifying tool and is our Rising Star; none of the others qualified.

In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, we ran SQLFluff 4.4.0 and Sqruff 0.40.0 on Linux against five small synthetic .sql files. One file was a simple table, index and row; one had a missing bracket; one had a partial index, view and update; one had a comment inside ELSE NULL; and one was a valid BEGIN IMMEDIATE transaction with a STRICT table. Both formatted the simple files the same way, left them unchanged on a second run, and rejected the missing bracket without changing that file. SQLite, in memory, produced the same tables, index and rows from the formatted files as from the originals. SQLFluff’s default fix removed the comment; Sqruff’s kept it. Both rejected the valid transaction. No real database was used. These observations match the published source code. They did not decide the Pick or the ranking, and the Prettier plugin was not part of the check. Earlier check record, October 3, 2026

ToolPublic sourcesWhat remains uncertain
SQLFluffREADME, command and rule documentation, default configuration, SQLite dialect source at 4.4.0 and on the main branch, release records to 4.5.0, issue reports 8562, 8792 and 8794, GitHub security advisories and page, PyPI and Homebrew records.How often its grammar gaps reject real migrations; when the proposed ST01 fix will be merged and released.
GoSQLXREADME, command guide, compatibility page, release records from version 1.0.0 to 1.17.0, GitHub security advisories page, Hacker News and GitHub topic listings.Its open issue reports; whether it reads BEGIN IMMEDIATE, savepoints, REINDEX, ANALYZE and STRICT tables; what format does with a file it cannot parse; how well its compatibility claims hold on real migrations.
SqruffREADME, documentation site, default configuration, SQLite dialect and command source at 0.41.0 and on the main branch, release records to 0.44.0, open and closed issue reports (2030, 3032, 5249, 5251, 5266 and 5291), GitHub security page, Hacker News post of February 12, 2024, PyPI and Homebrew records, Tobiko Data and Fivetran announcements, UK Companies House record, the quary.dev address.Who is responsible for the project after Quary’s acquisition; whether the other release programs include parse; whether the AM02 rule runs by default.
Prettier plugin SQL-CSTPlugin and parser READMEs, style guide, parser grammar source, issue reports 9 and 140, release records to 0.25.1, SQL Formatter README, Prettier command documentation, npm records.How it handles real migration files beyond its own tests; when the comment-ordering report will be fixed.

None of this establishes how any tool behaves on your files or your database. Next substantive review is due December 19, 2026, or sooner if SQLFluff or Sqruff adds the missing SQLite transaction syntax, the open SQLFluff ST01 report is resolved, or Sqruff’s ownership is clarified. Found a changed release or behavior? Contact the editors.

Sources and evidence

Sources were checked October 20, 2026 unless another date is given; repository, release and issue pages marked November 12, 2026 were read on that date. Documentation and source code establish intended behavior, not results on your files. Issue reports are attributed experiences, not failure rates.

Licences from each project’s repository, read again on November 12, 2026: SQLFluff MIT; GoSQLX Apache-2.0; Sqruff Apache-2.0; the Prettier SQL-CST plugin GPL-3.0-or-later and its parser GPL-2.0-or-later. None of the four has a price, plan or paid tier. OSV listed no advisory for Sqruff on PyPI or crates.io, or for the plugin on npm, on October 20, 2026; for SQLFluff it listed the three advisories above. This is a researched comparison, not a product review. Method: evidence standard, editorial picks.