Download the PHP package kostantinoabate/complihance without Composer
On this page you can find all versions of the php package kostantinoabate/complihance. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download kostantinoabate/complihance
More information about kostantinoabate/complihance
Files in kostantinoabate/complihance
Package complihance
Short Description Laravel package for cookie consent, policies and consent tracking
License MIT
Homepage https://github.com/kostantinoabate/complihance
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package complihance
Complihance
A Laravel package for cookie consent, policy acceptance, consent persistence, Google Consent Mode, cookie scanning and blocked embedded content.
FULL DOCUMENTATION WILL BE AVAILABLE SOON!
✅ Ready-to-use cookie banner
✅ Consent preferences page
✅ Granular vendor consent
✅ Google Consent Mode support
✅ Consent audit log and retention
✅ Cookie, storage and script scanner
Installation
Install the package via Composer:
Run the install command:
Run the migrations:
Publish editable data files:
Setup
Add the Complihance scripts to your main layout, preferably inside the <head>:
Render the default banner before the closing </body> tag:
Example:
Preferences page
To let users update or revoke their consent, render the preferences component in any Blade view:
Cookie policy table
Render a cookie/technology table:
Render only one category:
Configuration
The config file is published to:
Main options:
When your cookie configuration changes, increment:
Users will be asked to renew their consent.
Data files
Editable data files can be published with:
Published files:
Consent categories
Default categories are:
necessaryanalyticsmarketingfunctional
Example category:
Technologies and vendors
Technologies are configured in technologies.json.
Example:
Enable vendor-level consent:
Google Consent Mode
Google Consent Mode is enabled by default.
Complihance renders the default consent state through:
Consent Mode values are updated automatically when the user saves or changes preferences.
Blocking embedded content
Complihance can prevent embedded content from loading before consent is granted.
Example:
Or with the Blade directive:
Frontend API
Complihance exposes a frontend API on window.Complihance.
HTTP API
Default API prefix:
Available endpoints:
Example payload:
Artisan commands
Export collected consents:
Export consents for a date range:
Apply retention rules:
Preview retention without changing data:
Scan cookies, storage and scripts:
Scan only HTTP Set-Cookie headers:
Scan a sitemap:
Export a scan report:
Compare two scans:
Reset local Complihance data:
Cookie scanner requirements
Browser-based scanning requires Playwright and Chromium:
In Docker/Linux environments, Chromium system dependencies may also be required.
Alternatively, use the HTTP-only scanner:
Testing
Run the test suite:
License
The MIT License (MIT). See LICENSE.md for more information.
All versions of complihance with dependencies
ext-simplexml Version *
illuminate/contracts Version ^11.0 || ^12.0 || ^13.0
spatie/laravel-package-tools Version ^1.93.1