Repo brief: ankane/pgsync

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T23:31:18.957Z · commit 57bdddf5db50

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 3w ago
• 4 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

pgsync is a command-line tool that synchronizes data between PostgreSQL databases with support for parallel transfers, schema flexibility, and sensitive data masking. Unlike pg_dump/pg_restore, it handles partial table syncs, schema differences (missing/extra columns), and related record fetching through variable substitution in WHERE clauses. Modular Ruby architecture: lib/pgsync.rb is the entry point; lib/pgsync/client.rb manages database connections; lib/pgsync/sync.rb orchestrates the sync flow; lib/pgsync/table_sync.rb handles per-table transfers; lib/pgsync/schema_sync.rb manages schema setup. CLI entry point is exe/pgsync. Configuration is YAML-based (config.yml,…

Start here

Open these first:

• lib/pgsync.rb — Main entry point and gem initialization; defines the public API surface for the pgsync tool.
• lib/pgsync/client.rb — Core abstraction managing database connections and query execution to source and destination PostgreSQL instances.
• lib/pgsync/sync.rb — Primary orchestrator for the data synchronization workflow, coordinating schema and table-level syncs.
• lib/pgsync/table_sync.rb — Implements row-level data transfer logic with parallel processing, filtering, and conflict handling for individual tables.
• lib/pgsync/schema_sync.rb — Handles schema creation and migration on the destination database to match the source structure.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository, then verify the Gemfile for dependencies and install via bundle install. The project is packaged as a gem; for local development, gem install -e pgsync in the repository root would make the `pg…

Daily commands:

The project is not a running service but a CLI tool. After installation, invoke via: pgsync (to sync all configured tables), pgsync --init (to generate .pgsync.yml), pgsync table1,table2 (to sync specific tables),…

…shortened for this brief.

Key cautions & unknowns

• Small team — 4 contributors active in recent commits
• Single-maintainer risk — top contributor 97% of recent commits
• Scorecard: marked unmaintained (0/10)
• PostgreSQL connection strings must be specified correctly in .pgsync.yml (no evidence of validation error messages in README). The tool wipes existing data when using --schema-first flag, requiring explicit user…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.