- Can I use orange-rt/anonymize-bundle in a Laravel application?
- No. It is a Symfony bundle built around Doctrine ORM entity metadata and the Symfony console, not Laravel Eloquent. There is no practical adapter path that is cheaper than writing a purpose-built Laravel anonymizer. Treat it as a design reference rather than a Composer dependency.
- What does orange-rt/anonymize-bundle actually do?
- It anonymizes Doctrine entity data by letting you mark fields and apply anonymization strategies, using Faker-based value substitution. It is intended to scrub personal data in databases used for staging, development, or other non-production environments. The goal is to support GDPR and privacy compliance with consistent field-level anonymization.
- How do I install orange-rt/anonymize-bundle?
- On Symfony with Doctrine, you would install it with Composer, register the bundle in config/bundles.php or AppKernel, annotate entity properties with the bundle's marker, and run its console command against a target database. You must first verify that its PHP, Symfony, Doctrine, and Faker constraints fit your application. Do not install it in a Laravel application.
- Which Laravel versions are supported by orange-rt/anonymize-bundle?
- None. This package is a Symfony bundle and does not provide a Laravel service provider, Eloquent integration, or Artisan commands. Laravel teams should not adopt it as a dependency. A custom Artisan command over a declarative field map is the realistic alternative.
- Does orange-rt/anonymize-bundle support PHP 8.2 and Doctrine 3?
- That is not established by the available package information and is unlikely without a fork. The bundle predates modern Doctrine attributes and PHP 8 conventions, and its Faker constraint may reference the abandoned fzaninotto/faker package. Treat compatibility with PHP 8.2 and Doctrine 3 as a spike item before adoption.
- Is orange-rt/anonymize-bundle actively maintained?
- The maintenance signal is weak: 5 stars, 0 dependents, and no evidence of recent activity. No dependents means there is little downstream production validation, so you would absorb much of the debugging burden. If you proceed on Symfony, budget for forking and owning the package.
- How does orange-rt/anonymize-bundle handle relationships and foreign keys?
- The available assessment does not establish how it handles relationships, FK columns, or joined and embedded entities. A key question for the maintainer is whether it uses a consistent fake-value mapping per record or a fresh random value per field occurrence. Referential integrity must be tested carefully, because inconsistent mapping can produce orphaned rows and broken joins.
- Does orange-rt/anonymize-bundle support dry runs and field-level anonymization strategies?
- Field-level anonymization strategies are the core of the package, but the availability of a dry-run mode is not confirmed. The assessment also flags the need to check for a table or entity allowlist and for null, fake, hash, or redact strategies. Ask the maintainer or inspect the code before relying on these controls.
- What should Laravel developers use instead for GDPR data anonymization?
- Write a purpose-built Artisan command over a declarative field map using fakerphp/faker. You can borrow the annotation-driven field-marking model as a design reference, but do not adopt the Symfony bundle itself. This gives you control over Eloquent relationships, JSON columns, custom casts, and referential integrity.
- What are the main production risks of adopting this bundle?
- The biggest risk is security theater: a partially anonymized dataset can be treated as safe while PII remains in JSON columns, embedded objects, custom Doctrine types, or free-text fields. Referential integrity and consistent fake-value mapping are also unresolved concerns. Add weak maintenance, no dependents, and a likely abandoned Faker dependency, and the overall technical risk is high.