Skip to content

Security: sql-devops/database-migration-tools

Security

SECURITY.md

Security Policy

Local-First Execution Model

Database Migration Studio runs on your workstation or CI runner. It never transmits schema metadata, connection strings, credentials, or table rows to external servers.

Credential and Secret Handling

  • ConnectionConfig.password is marked skip_serializing in Rust so exported plan.json files, report.json, report.html, and local state.db job records do not store database passwords.
  • Debug formatting on connection configs prints [REDACTED] in place of secrets.
  • CLI execution reads passwords from DBMIGRATE_SOURCE_PASSWORD and DBMIGRATE_TARGET_PASSWORD environment variables or OS credential storage.
  • SQL identifiers are quoted per dialect (quote_ident_pg, quote_ident_mysql, quote_ident_sqlite), embedded quotes are doubled, and NUL bytes are rejected. Values are bound via parameterized queries.

Reporting a Vulnerability

If you discover a SQL injection path, secret leak in logs or reports, or data-loss edge case, open a private security advisory on GitHub at https://github.com/sql-devops/database-migration-tools/security/advisories/new.

There aren't any published security advisories