Weave Code
Cookie Consent Bundle Laravel Package
indigophp/cookie-consent-bundle
Symfony bundle for GDPR-friendly cookie consent. It shows a customizable consent banner, lets visitors accept or reject cookie categories, and stores their choices so analytics, tracking, and other scripts load only after permission is granted.
Symfony Bundle for the popular Cookie Consent plugin
Frequently asked questions about Cookie Consent Bundle
- Can I install indigophp/cookie-consent-bundle in a Laravel application?
- No, not as a dependency. It is a Symfony bundle that registers through AppKernel and relies on a Symfony DI Extension and Twig, none of which Laravel provides. The technical evaluation records it as not installable as-is for Laravel, and the realistic path is to borrow the JS/CSS assets and reimplement the wrapper natively. Composer constraints are likely Symfony 2/3-era, so installation would conflict or require platform-requirement hacks.
- Does this package support Laravel 10 or Laravel 11?
- No. The repository is archived and has no Laravel package discovery, facade, middleware, Blade view, or vendor:publish tags. It targets Symfony 2/3-era Symfony, so a Laravel 10/11 app on PHP 8.2+ is a double version skew. There is no evidence of PHP 8.x or modern Laravel compatibility work.
- Is indigophp/cookie-consent-bundle GDPR compliant for EU or UK traffic?
- Not by itself. It provides a front-end notice banner, not a consent management platform; GDPR and ePrivacy require prior opt-in for non-essential cookies, granular per-category control, consent records, and revocation. A banner leaning on implied or continued-browsing consent does not satisfy that. The legal exposure is larger than the engineering exposure, so legal or privacy sign-off is needed.
- How do I install and configure the cookie consent bundle?
- In Symfony you would register the bundle in AppKernel, rely on its DI Extension configuration tree, and render the UI with Twig. In Laravel there is no equivalent bundle lifecycle, so there is no supported install path. If you only want the UX, copy the JS/CSS from Resources, write a config file, and build a Blade component plus a small service provider.
- What is the difference between a cookie notice and a consent management platform?
- A notice banner displays information but may rely on implied consent; a consent management platform blocks non-essential scripts before opt-in, records consent choices, supports granular categories, and allows revocation. This package is described as a configurable banner that remembers consent, not a full CMP. For EU or UK obligations you need blocking, logged, revocable consent, which likely rejects this package outright.
- Can I use the bundle's JavaScript and CSS assets without the Symfony PHP code?
- Yes, that is the portable part. The evaluation says the genuinely portable artifacts are the front-end Cookie Consent JS/CSS assets and the default consent configuration array. You would vendor those assets, write your own Laravel config, Blade component, and service provider, and remove the Composer requirement. That is roughly 50 to 150 lines of your own code plus asset handling.
- Is this package maintained and safe for production?
- No. The repository is archived, with 15 stars, 0 dependents, and no production evidence. There are no security patches, no PHP 8.x or Laravel 10/11 work, and no upstream responsiveness for the bundled Cookie Consent plugin. If you vendor the assets, you permanently own a forked JS asset with no upstream.
- Does it support Google Consent Mode v2 or tag gating for GA4 and Meta?
- Not in the provided context. The package wraps a front-end notice banner and does not claim tag gating, blocking GA4, Meta, LinkedIn, or Hotjar before opt-in, or Google Consent Mode v2 for ad measurement. If EU paid media is on your roadmap, that requirement is entirely out of scope for this bundle. You would need a CMP or a custom gating layer.
- What are alternatives for cookie consent in Laravel?
- The context does not name alternatives, but it recommends rejecting this package as a dependency and retaining it as a reference source. If you want this UX, vendor the JS and reimplement the wrapper natively in Laravel with a Blade component and service provider. Evaluate maintained Laravel-native consent packages or a dedicated CMP against your GDPR blocking, logging, and revocation requirements.
- How should I test cookie consent behavior in a Laravel app?
- Test that non-essential scripts are blocked before opt-in and load only after consent, and that choices persist and can be revoked. Also test granular category acceptance, consent record capture, and behavior for EU or UK visitors versus other jurisdictions. Because this package has no Laravel integration, any tests would target your own reimplementation rather than the Symfony bundle.
Weaver
How can I help you explore Laravel packages today?