Weave Code
Foggy Laravel Laravel Package
worksome/foggy-laravel
Foggy for Laravel anonymizes sensitive model data with configurable fogging strategies, making GDPR-style deletion and redaction simple. Define how each Eloquent attribute should be masked, replaced, or hashed, and let Foggy handle the rest automatically when users request erasure.
A Laravel wrapper for Foggy
Frequently asked questions about Foggy Laravel
- What does worksome/foggy-laravel do?
- It is a Laravel wrapper around Foggy that anonymizes sensitive model data using configurable fogging strategies. You define how each Eloquent attribute should be masked, replaced, or hashed, and Foggy applies those rules when data needs to be erased or redacted. It is aimed at GDPR-style deletion workflows.
- How do I install worksome/foggy-laravel?
- Install it with Composer using composer require worksome/foggy-laravel, then publish the configuration file with php artisan vendor:publish. Laravel package auto-discovery registers the service provider, so no manual wiring is usually required. Check the package README for the exact config tag and any additional setup steps.
- How do I define a fogging strategy for an Eloquent model?
- You typically create a fogging strategy class or configuration that maps model attributes to masking, replacement, or hashing behaviour. The package lets you declare per-attribute rules so names, emails, or other sensitive fields are handled consistently. Refer to the package documentation for the exact strategy contract and registration syntax.
- Which Laravel and PHP versions does worksome/foggy-laravel support?
- The package is pre-1.0 at v0.8.1, so you should check its composer.json for the declared illuminate/support and PHP constraints. Because it is a Laravel wrapper, support generally follows the Laravel versions the maintainer tests against. Pin the package and verify compatibility before upgrading your framework.
- Is worksome/foggy-laravel safe for production use?
- It is a pre-1.0 package, so semver allows breaking changes in minor releases; pin to an exact or tilde-constrained version and review upgrades. It is designed as a background and ops utility rather than request-path middleware, which keeps it off the hot path. Test your fogging strategies against a staging copy of real data before relying on them for erasure.
- How do I test that my fogging strategies anonymize data correctly?
- Write feature tests that create model records with known sensitive values, run the fogging process, and assert the stored attributes are masked, replaced, or hashed as expected. Use database transactions or RefreshDatabase so test data does not persist. Also test edge cases such as nulls, relations, and unique-constrained columns.
- Does Foggy handle relationships and related models?
- The package is focused on anonymizing model attributes, and how relations are treated depends on the strategies you define and any cascading you implement. For GDPR erasure you should explicitly decide whether related records are fogged, deleted, or left untouched. Confirm the behaviour in the package documentation and cover it in tests.
- What are alternatives to worksome/foggy-laravel for GDPR data anonymization?
- Alternatives include writing custom anonymization jobs, using database-level masking, or adopting a dedicated GDPR erasure package. Foggy's value is the declarative, per-attribute strategy configuration inside Laravel. Evaluate whether you need reversible redaction, audit logging, or hard deletion before choosing.
- How is worksome/foggy-laravel maintained and when will it reach 1.0?
- The project is at v0.8.x, indicating active pre-1.0 development; release cadence and issue responsiveness should be checked on the GitHub repository. There is no guaranteed 1.0 timeline, so treat upgrades as reviewable events. Watch the changelog for breaking changes between minor versions.
- Can I use worksome/foggy-laravel for scheduled or queued erasure jobs?
- Yes; because it is a Laravel package, it can be invoked from queued jobs or the scheduler like any other service. In multi-node deployments, guard scheduled jobs with onOneServer or a dedicated worker to avoid duplicate processing. Keep long-running anonymization batched and idempotent.
Weaver
How can I help you explore Laravel packages today?