Weave Code
Cookie Bundle Laravel Package
kunstmaan/cookie-bundle
KunstmaanCookieBundle is a Symfony bundle for cookie consent management. It provides a configurable cookie bar, cookie categories, and a policy page to help sites comply with GDPR and ePrivacy requirements, with Twig templates and easy integration into Kunstmaan CMS projects.
The Kunstmaan Cookie Bundle adds cookie consent management to Symfony applications, helping you present cookie information and collect user preferences in a GDPR-friendly way. It provides configurable cookie categories, a consent banner, and templates you can adapt to your site’s design.
- Configurable cookie categories and descriptions
- Consent banner with accept/decline controls
- Customizable templates and translations
- Integration with Kunstmaan CMS and Symfony projects
- Centralized cookie policy management
Frequently asked questions about Cookie Bundle
- Is kunstmaan/cookie-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. It ships a KunstmaanCookieBundle class, a DependencyInjection extension with a configuration tree, Twig templates, and service definitions wired through Symfony's container. There is no Laravel service provider, no Blade views, no facade, and no publishable Laravel config file.
- Can I use kunstmaan/cookie-bundle in a Laravel application?
- Composer may resolve it inside a Laravel project because Laravel consumes Symfony components, but the bundle will never be registered by Laravel's kernel. None of its routes, Twig rendering, or container wiring will activate. Real integration means forking and porting to Blade views, a config file, a service provider, and middleware for consent state, or reusing only its markup as a design reference.
- Which Symfony versions does KunstmaanCookieBundle support?
- The last release is dated 2021-11-07, which places the bundle in the Symfony 4/5 era. Compatibility with Symfony 6 and Symfony 7 is unverified and would likely require constraint edits plus Twig API adjustments. Test on a branch before assuming it installs cleanly.
- Does KunstmaanCookieBundle block non-essential scripts before consent?
- Based on the available information, the bundle delivers a cookie bar, a detailed preference pop-up, and a cookie policy page, all of which are presentation-layer artifacts. There is no evidence of pre-consent script blocking or consent enforcement. If script injection is not intercepted, the banner can create a false sense of compliance.
- Does the bundle record cookie consent server-side for GDPR audits?
- There is no evidence of server-side consent persistence, consent versioning, audit logging, or scope tracking. Those are the parts that actually carry compliance weight in an enforcement action. You would need to build that layer yourself or pair the front end with a dedicated consent management platform.
- Is kunstmaan/cookie-bundle actively maintained?
- It is a read-only subtree split of the KunstmaanBundlesCMS monorepo, and the last release was 2021-11-07. It has 0 stars and 0 dependents, so there is no public consumer base exercising the code and no issue backlog to mine for known breakage. Plan for it as unmaintained.
- How do I install and configure KunstmaanCookieBundle in a Symfony app?
- Install it with Composer, register the bundle in your bundles configuration, then define cookie categories through the bundle's DependencyInjection configuration tree. Rendering uses the bundle's Twig templates, so theming and translations follow Symfony conventions rather than Laravel ones. Because the release predates Symfony 6, expect to pin or adjust framework constraints.
- Is the license permissive enough to fork KunstmaanCookieBundle?
- The license is not stated in the information provided, so check the LICENSE file in the repository before planning a fork. Kunstmaan bundles are commonly released under permissive terms, but verify rather than assume. If you fork, you own maintenance, Symfony and Twig upgrades, and every future compliance update.
- What should I use instead for cookie consent in Laravel?
- A purpose-built Laravel consent package or a hosted consent management platform will cover consent logging, policy versioning, and script blocking that this bundle does not. If you only want the interaction pattern, extract the cookie-category model and the bar/modal flow as a design reference and rebuild them with Blade components. A short spike is a sensible budget for that extraction.
- Does it support Google Consent Mode v2 or TCF / IAB vendor handling?
- No. A 2021 release predates Consent Mode v2 and current EDPB and CNIL reject-button parity expectations, and it has no TCF vendor handling. If a requirement mandates a certified CMP, no homegrown banner will satisfy it regardless of which package you start from.
Weaver
How can I help you explore Laravel packages today?