Download the PHP package ginkelsoft/laravel-compliance-hub without Composer
On this page you can find all versions of the php package ginkelsoft/laravel-compliance-hub. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ginkelsoft/laravel-compliance-hub
More information about ginkelsoft/laravel-compliance-hub
Files in ginkelsoft/laravel-compliance-hub
Package laravel-compliance-hub
Short Description Umbrella package for the GinkelSoft GDPR/AVG compliance family. Installing this single package pulls in retention, right-to-be-forgotten, subject access, consent and breach registry, and exposes a compliance:verify command that checks every audit-log chain in one shot.
License MIT
Informations about the package laravel-compliance-hub
Ginkelsoft Laravel Compliance Hub
Overview
Umbrella for the GinkelSoft GDPR / AVG compliance family. Installing this single package pulls in every member of the family and adds two Artisan commands that operate across all five audit-log chains in one shot:
compliance:verify— runsHashChain::verify()on every audit-log table in the family. Exits non-zero when at least one chain is tampered or otherwise unverifiable. Perfect for a scheduled job that pages whoever is on call.compliance:report— bundles row counts and verify status per chain into a single Markdown or JSON report. No personal data — only counts and status, safe to drop into a board pack.
This package is the art. 5(2) accountability evidence-generator for
the family. It owns no migrations and no models of its own; everything
it does is built on top of Ginkelsoft\ComplianceCore\Support\HashChain
and the per-control packages' audit tables.
The family
Installing this package installs the whole family.
| Package | GDPR Article(s) | Role |
|---|---|---|
laravel-compliance-core |
art. 5(2) | Shared primitives |
laravel-data-retention |
art. 5(1)(e) | Storage limitation |
laravel-data-right-to-be-forgotten |
art. 17 | Subject-driven erasure |
laravel-data-subject-access |
art. 15 + 20 | Subject access |
laravel-data-consent |
art. 6(1)(a) + 7 | Consent registry |
laravel-data-breach-registry |
art. 33 + 34 | Breach registry |
laravel-compliance-hub |
art. 5(2) | Umbrella + verify/report — this package |
Installation
Composer pulls in core + the five functional packages automatically. Then publish each one's config and migrations:
Then add a single shared signing secret to .env:
This one secret signs every chain — retention, forget, subject access, consent, breach. Rotate it only as part of an explicit, documented audit rotation procedure.
Usage
Verify every chain in one shot
Output:
Schedule it:
Exit code is 0 when every present chain verifies, 1 when at least
one chain fails. Tables that are not present in the schema (a family
package whose migration has not been run) are reported as — (table missing) and do not count as a failure — so a partial install does
not page anyone.
Bundled report
The report contains row counts and verify status per chain, plus a "generated_at" timestamp. No personal data. Suitable for handing to the DPO every month or pasting into a board pack as evidence of art. 5(2) accountability.
What the hub does NOT do
- It does not modify any data. It only reads the audit logs to verify hashes; it never writes.
- It does not own its own tables. Every chain it verifies is the responsibility of one of the family packages.
- It does not enforce a UI. Verify + report are CLI-first; build your own Filament / Nova / Livewire layer on top if you want a dashboard.
Compliance notes
- GDPR art. 5(2) — Accountability. The bundled report + scheduled verification together are the operational realization of this principle: evidence that every control is in place and every audit trail is internally consistent.
This package is not legal advice. The judgements that produce the data this package verifies — retention periods, severity assessments, DPIA decisions — belong to your DPO.
Testing
Reporting bugs
Found a bug or unexpected behaviour? We want to hear about it.
Preferred — open a GitHub issue: https://github.com/ginkelsoft-development/laravel-compliance-hub/issues/new
When opening an issue, please include:
- Versions — PHP, Laravel, and
ginkelsoft/laravel-compliance-hub(composer show ginkelsoft/laravel-compliance-hub). - What you did — the artisan command, code snippet, or steps that triggered the bug.
- What you expected vs what actually happened — include full error output or a stack trace if there is one.
- A minimal reproduction if you can — a failing test or a small code sample beats a long description.
Security-sensitive findings (anything that could expose personal data, break a hash-chain, or bypass an audit log) — please do not open a public issue. E-mail [email protected] directly with "SECURITY" in the subject line and we will respond privately.
Not on GitHub? You can also e-mail [email protected] with the same information.
Contact
For commercial support, integration questions, or anything that doesn't fit a GitHub issue: [email protected] — https://ginkelsoft.com.
License
MIT License — see LICENSE. (c) 2026 Ginkelsoft
All versions of laravel-compliance-hub with dependencies
illuminate/support Version ^10.0 || ^11.0 || ^12.0 || ^13.0
illuminate/database Version ^10.0 || ^11.0 || ^12.0 || ^13.0
illuminate/console Version ^10.0 || ^11.0 || ^12.0 || ^13.0
ginkelsoft/laravel-compliance-core Version dev-development
ginkelsoft/laravel-data-retention Version dev-development
ginkelsoft/laravel-data-right-to-be-forgotten Version dev-development
ginkelsoft/laravel-data-subject-access Version dev-development
ginkelsoft/laravel-data-consent Version dev-development
ginkelsoft/laravel-data-breach-registry Version dev-development