Weave Code
Gdpr Bundle Laravel Package
nucleos/gdpr-bundle
Nucleos GDPR Bundle is a Symfony bundle for GDPR compliance. It provides cookie consent management, personal data anonymization, and configurable privacy tools to help applications meet EU data protection and data subject request requirements.
nucleos/gdpr-bundle is a Symfony bundle that helps you bring your application into compliance with the GDPR. It provides ready-made tools for the two core data-subject rights—data portability and erasure—so you can implement them without building the workflow from scratch.
The bundle exposes a clean, event-driven API: register your entities, and it handles collecting a user's personal data into a downloadable archive or anonymizing/removing it on request. It integrates with Doctrine and the Symfony framework, letting you plug in custom data providers where needed.
- Data export (portability) with pluggable collectors
- Data anonymization and erasure workflows
- Symfony DI integration and Doctrine support
- Extensible, event-based architecture
- Configurable to fit your existing entities
Install it via Composer and wire it into your app in minutes.
Frequently asked questions about Gdpr Bundle
- Can I install nucleos/gdpr-bundle in a Laravel application?
- Not as a drop-in dependency. It is a Symfony bundle built around Symfony's container, configuration, event dispatch, Twig integration, and bundle conventions, while Laravel uses a different container, middleware model, Blade, and package discovery. The evaluation treats direct Laravel compatibility as effectively absent, so use it only as reference unless you fork and heavily adapt it.
- Does nucleos/gdpr-bundle support Laravel 11 or Laravel 12?
- No supported Laravel version is indicated; the package is a Symfony bundle, not a Laravel package. Its Symfony bundle glue, configuration schema, and Twig assumptions would need replacement. Treat any Laravel 11 or 12 use as a custom port, not normal Composer compatibility.
- What does nucleos/gdpr-bundle actually provide?
- The evaluation describes it as a narrow Symfony bundle for GDPR-conform cookie information and banner behavior. It is not a general consent-management platform or a full data subject request workflow engine. Features such as consent logging, granular preferences, withdrawal, renewal, audit evidence, or export and deletion may require additional implementation.
- Is nucleos/gdpr-bundle maintained and safe for production?
- It is archived, has 11 stars, zero dependents, and a last release in August 2024, which signals low community validation and no active maintenance. Archived packages may still run, but they will not receive security patches, framework compatibility updates, or legal-content corrections. For production, the organization would own fork maintenance and compliance review.
- What are the best Laravel alternatives to a Symfony GDPR cookie bundle?
- The evaluation recommends deciding between a small internal Laravel package and a maintained Laravel-native consent package. It does not name a specific alternative, so verify maintenance, consent-record support, script blocking, withdrawal, and audit logging before adoption. If no approved vendor exists, build with Laravel middleware, Blade components, configuration, and a persistence layer for consent records.
- Can I use this bundle for GDPR consent logging and audit evidence?
- The assessment warns that cookie banners are only one part of GDPR and consent obligations. This bundle's documented scope is cookie information or banner behavior, and the evaluation says consent logging, granular preferences, withdrawal, renewal, and audit evidence may not be covered unless extended. Confirm legal evidence requirements before relying on it.
- Does nucleos/gdpr-bundle handle data subject export and deletion requests?
- The short blurb mentions data subject request workflows including export and deletion, but the technical evaluation characterizes the package's purpose as narrow cookie information for Symfony applications. It explicitly says the package is not a general data subject request workflow or compliance engine. Do not assume export and deletion are covered without inspecting the code and testing the exact workflow.
- How would I port nucleos/gdpr-bundle behavior to Laravel?
- Use the bundle as design input rather than lifting and shifting it. Inventory cookie usage and legal requirements, review its behavior and templates as reference, then implement consent capture, preference storage, script blocking, and audit logging as separate Laravel concerns. Sequence the work as a compliance feature with discovery, legal review, a small Laravel-native prototype, privacy review, and a low-risk pilot.
- Is it worth forking nucleos/gdpr-bundle for a Laravel project?
- Only if the team accepts owning maintenance and compliance review. The bundle is archived, so a fork would need Symfony compatibility work or a rewrite of bundle glue, configuration, and Twig assumptions for Laravel. A tightly timeboxed prototype can confirm reuse boundaries, but the evaluation recommends extracting requirements and building Laravel-native behavior instead.
- How should I test a Laravel cookie consent implementation based on this bundle?
- Test consent capture, preference storage, script blocking, withdrawal, renewal, and audit evidence as separate behaviors. Validate the UI and legal copy with privacy stakeholders, and cover supported jurisdictions, languages, and retention rules. Because direct Laravel compatibility is absent, do not treat a Symfony bundle test suite as proof of Laravel integration.
Weaver
How can I help you explore Laravel packages today?