sqitchers/sqitch

Sensible database change management

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 21st, 2026
Created on January 27th, 2012
Open Issues & Pull Requests: 84 (+0)
GitHub issues: Enabled
Number of forks: 214
Total Stargazers: 3,167 (+0)
Total Subscribers: 54 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.8 hours
Mean response time: 15.7 days
90th percentile: 18.1 days
Tracked items: 57

How this project is maintained

90% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "engine" is answered fastest, typically in about 3 hours, while "waiting" waits about 29 hours. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 21
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 987 days
Stale 30+ days: 19
Stale 90+ days: 18

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • engine (19)
  • bug (17)
  • waiting (16)
  • patched (11)
  • todo (7)
  • feature (6)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Sqitch is a database change management application that enables version control for database schemas across multiple database engines without tying users to any particular framework or platform.

The tool addresses the problem of safely tracking and deploying database schema changes by using native SQL scripts specific to each database engine rather than an abstraction layer. Changes can declare dependencies on other changes, ensuring correct execution order even when commits arrive out of sequence. Sqitch employs a Merkle tree pattern similar to Git to verify deployment integrity through a plan file, eliminating the need for sequential numbering of migrations. Until changes are tagged and released, developers can modify deployment scripts iteratively, supporting test-driven database development workflows.

Sqitch suits teams managing schemas across PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, or ClickHouse who want a framework-agnostic approach. It works well for projects requiring cross-database compatibility or those where database changes need to be coordinated with changes from other Sqitch projects through explicit dependency declarations. The tool is particularly valuable when iterative schema development matters more than locking changes immediately upon commit.

The project maintains active development with regular updates and comprehensive documentation including tutorials tailored to each supported database engine. The codebase shows sustained attention to supporting an expanding range of database platforms, with recent additions extending compatibility to newer systems. Development activity demonstrates ongoing refinement of core functionality and continued investment in making the tool accessible across diverse database environments.