Anonymizer Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy on privacy tooling: The Anonymizer library (now with a 1.0 Symfony integration) gives you a vetted, configurable data-anonymization layer instead of hand-rolling PII scrubbing. For any roadmap item touching personal data, this is the default "buy/open-source" option to evaluate before greenlighting custom work.
• Safe non-production data: Enables a repeatable pipeline for cloning production datasets into staging/dev/QA with PII removed — a frequent prerequisite for faster iteration, realistic test fixtures, and demos.
• Compliance-driven features: Directly supports GDPR/CCPA/HIPAA-adjacent requirements (right-to-erasure workflows, data-sharing with partners, analytics exports) where raw identifiers must be masked but structure must be preserved.
• Granular control as a product requirement: The 1.0 release exposes toggles for caching, loader, and exclusion strategies — meaning product can specify "mask these fields, preserve those" rather than accept all-or-nothing scrubbing.
• Platform maturity signal: A 1.0 Symfony bundle indicates the core library has stabilized its integration surface. Worth tracking for the Laravel side, but note this release does not ship first-party Laravel integration.

When to Consider This Package

Adopt when:

• You must anonymize or pseudonymize structured datasets (DB dumps, exports, logs) before they leave a trusted boundary.
• Your team is on Symfony, or willing to wire the core library manually into Laravel — the 1.0 bundle is Symfony-specific.
• You need configurable behavior (cache on/off, loader on/off, exclusion strategies) rather than a fixed script.
• Compliance, security, or data-governance stakeholders have flagged PII in non-prod environments.

Look elsewhere when:

• You need first-party Laravel support — this release provides Symfony integration only; expect custom service-provider/config work to use it in Laravel.
• Requirements demand streaming/real-time anonymization at high throughput, format-preserving encryption, or complex referential-integrity-preserving pseudonymization beyond what exclusion strategies cover.
• You need vendor SLAs or commercial support; this is an open-source library with a 1.x integration, not a managed service.
• You are pre-product-market-fit and a simple faker-based fixture generator already covers your needs.

How to Pitch It (Stakeholders)

For executives: This is an open-source data-anonymization library reaching a 1.0 integration milestone. Adopting it reduces privacy/compliance risk (GDPR, CCPA) by letting us mask personal data before it reaches non-production environments or third parties — without building and maintaining bespoke scrubbing code. Low cost, mature upstream project, configurable to our policy needs. The 1.0 is Symfony-oriented; a small amount of Laravel glue work is required, which we should scope.

For engineering: The 1.0 release adds a Symfony bundle around the PHPSharkTank Anonymizer core, with toggles for caching, loader, and exclusion strategies. The configurable exclusion strategies are the useful part — they let you declare what to keep (e.g., IDs for join integrity) versus what to scrub. For Laravel, plan to consume the core library directly and wrap it in a service provider + config; the Symfony bundle is a useful reference for wiring and configuration shape but is not drop-in.

Recommendation: Evaluate the core library now for any PII-in-non-prod or data-sharing initiative; do not assume Laravel support from this release. Track upstream for a Laravel integration or budget a thin internal adapter.