# GreenmaskIO/greenmask

Database anonymization and test data management

Repository: https://github.com/GreenmaskIO/greenmask
Canonical: https://ross.abutalabs.com/products/greenmask
Homepage: https://greenmask.io
Language: Go
License: Apache-2.0
License Family: permissive
Topics: golang, obfuscation, postgresql, security, security-tools, anonymization, synthetic-data, go, pg, testing-tools, dba, faker, database, data-masking, mysql, differential-privacy, backup, dump, sql-dump, mysqldump
Last push: 2026-08-25T18:17:22+00:00

## Health v2 (maintenance only)
Score: 93/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 99, longevity 71
- inputs: {"age_days": 1006, "days_push": 8, "days_rel": 11, "gap_med": 24, "n_releases_24m": 24}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1750, forks 67 (observed 2026-08-28T04:05:31.087521+00:00)

## What it is
Greenmask is an open-source CLI utility for logical database dumping, anonymization, synthetic data generation, and restoration, production-ready for PostgreSQL with MySQL support in beta. It is stateless, requires no schema changes, and produces dumps compatible with standard tools like pg_restore and mysqldump.

## Use cases
- anonymize production data before sharing with developers
- generate synthetic test data that looks like production
- create smaller referentially intact dev database subsets
- mask PII in database dumps for staging environments
- dump PostgreSQL database to S3 with transformations applied
- keep masked data consistent across dumps with deterministic transformations
- integrate database anonymization into CI/CD pipelines

## When to choose
- you need to anonymize or mask PostgreSQL data in logical dumps without changing the schema
- you want deterministic, reproducible masking with referential integrity and constraint awareness
- you need database subsetting or S3-compatible backup storage
- you want a stateless tool compatible with pg_restore

## When to avoid
- you need MySQL anonymization in production (still beta)
- you need anonymization for databases other than PostgreSQL and MySQL
- you want a GUI-driven data masking platform
- you need real-time or in-database masking rather than dump-based

## Facets
- artifact type: cli-tool
- maturity: active
- function: security, database, backup, data-generation, developer-tools, cli
- domain: databases, security, privacy, developer-tools, testing
- platform: windows, cli, cross-platform
- tags: data-masking, anonymization, synthetic-data, postgresql, mysql, database-subsetting, pg-dump, test-data-management, s3-storage, gdpr, data-engineering, linux, macos, docker

## Member repositories
- GreenmaskIO/greenmask (main) score 93

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:31.087521+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:28:34.428195+00:00, confidence not recorded.
  - readme: https://github.com/GreenmaskIO/greenmask (fetched 2026-08-28T04:05:31.087521+00:00, sha 9a7eacbfa0c9)
  - homepage: https://greenmask.io (fetched 2026-08-29T11:06:33.779283+00:00, sha 805ffe169f7a)
  - site_page: https://www.greenmask.io/about (fetched 2026-08-29T11:06:33.788314+00:00, sha b6fd1091b670)
  - site_page: https://docs.greenmask.io/latest (fetched 2026-08-29T11:06:33.790264+00:00, sha 0b9a5834baa8)
- Data as of 2026-08-30T08:39:29.467469+00:00.