Weave Code
Cookie Consent Bundle Laravel Package
nowo-tech/cookie-consent-bundle
A PHP package for adding customizable cookie consent banners and privacy preference controls to web applications. Configure consent categories, manage scripts, and support compliance with a lightweight, integration-friendly setup.
nowo-tech/cookie-consent-bundle is a lightweight Symfony bundle that adds a configurable, GDPR-friendly cookie consent banner to your application. Define cookie categories, remember visitor choices, and block optional scripts until consent is granted—all through simple configuration, with no build step required.
- Category-based consent management (necessary, analytics, marketing)
- Accept all, reject all, and granular settings options
- Persistent consent storage with automatic re-consent handling
- Twig integration with translatable UI strings
- Script blocking until the matching category is approved
Frequently asked questions about Cookie Consent Bundle
- Can I use nowo-tech/cookie-consent-bundle in a Laravel application?
- Not directly. It is a Symfony bundle built on Symfony's DI container, bundle discovery, Twig, and kernel event subscribers, none of which load in a Laravel app. Composer will install it, but the banner, configuration tree, and consent logging will not boot without an adapter or a port. Treat it as a design reference rather than a drop-in dependency.
- Is this package Laravel-compatible or Symfony-only?
- Symfony-only. Its value is delivered through Symfony-specific glue: a Bundle class, a DI Extension with a Configuration tree, compiler passes, Twig templates, and event subscribers. Laravel's service providers, config publishing, Blade, and middleware have no interoperability with Symfony's container or bundle discovery. There is no supported route to mounting it inside Laravel.
- What features does the bundle provide for GDPR cookie consent?
- It renders a GDPR cookie consent modal with category toggles, submits preferences via AJAX, optionally logs consent records, and supports a configurable Doctrine table prefix. The blurb also states it blocks non-essential scripts until visitors agree. That is a reasonable feature set for a Symfony app, but each piece is coupled to Symfony and Doctrine internals.
- How much work is it to port this bundle to Laravel?
- Plan on a partial rewrite, not a wrapper. The evaluation budgets a 1-2 day source audit spike, then a decision between porting roughly 300-600 lines of domain logic into a Laravel package or reimplementing from scratch. You will need an Eloquent repository, a request shim for HttpFoundation, and Blade or Livewire components to replace the Twig UI. Budget it as greenfield work with a reference.
- Which parts of the bundle are reusable in a Laravel project?
- A bounded subset: the consent-category model and toggles, the cookie-consent record shape, and the optional consent-logging persistence logic. Even those are likely coupled to Doctrine ORM entities and Symfony HttpFoundation Request, so they need adapters before a Laravel service provider can use them. Extract the category/config schema, the consent record fields, the client-side state machine, and the script-gating mechanism into a one-page spec.
- Does the bundle block non-essential scripts before consent?
- The package blurb says it blocks non-essential scripts until visitors agree, which is the opt-in behavior EU regulators expect. However, you should verify the actual gating mechanism in the source before relying on it, because a subtle default error in a consent path is a legal exposure, not just a bug. Confirm how consent state is stored client-side and whether it records a timestamp, policy version, and category set.
- Is nowo-tech/cookie-consent-bundle safe for production GDPR compliance?
- Be cautious. The package has 0 stars, 0 dependents, a single apparent maintainer, and no external production validation or security disclosure process. The evaluation also notes a metadata anomaly, a last release dated in the future, so verify the CHANGELOG and tag history. Because the code sits directly in the GDPR consent path, an unmaintained or subtly incorrect implementation is a legal risk. Do not adopt it as a runtime dependency for a compliance-critical Laravel app.
- Are there tests and CI for this package?
- The technical evaluation flags no evidence of a test suite, and calls zero tests in a compliance path a stop signal. It also asks whether a CI matrix exists and what PHP, Symfony, Twig, and Doctrine version constraints are declared. Before any commitment, inspect the repository for a test suite and a CI matrix. If it targets Symfony 5/6 only with no tests, that signals stagnation.
- What should I check before committing to this package?
- Resolve the key questions: exact PHP, Symfony, Twig, and Doctrine constraints and whether CI exists; whether consent logging is abstracted behind an interface or hard-wired to Doctrine entities; how consent state is stored client-side and what audit fields it records; and whether the modal is opt-in by default. Also confirm who maintains it and their commitment to security patches. Treat the future-dated release as a tagging artifact until proven otherwise.
- What Laravel alternatives should I consider instead of this Symfony bundle?
- The evaluation recommends comparing against two Laravel-native cookie consent alternatives and a roughly two-week in-house build before deciding. A Laravel-native package will give you Blade components, a service provider, config publishing, middleware, and Eloquent persistence without an adapter layer. If you like this bundle's design, adopt the design and build the code: extract its category schema and consent-record contract, then rebuild the UI and logging in Laravel.
Weaver
How can I help you explore Laravel packages today?