PHP download

Download the PHP package ginkelsoft/laravel-data-breach-registry without Composer

On this page you can find all versions of the php package ginkelsoft/laravel-data-breach-registry. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download ginkelsoft/laravel-data-breach-registry
More information about ginkelsoft/laravel-data-breach-registry
Files in ginkelsoft/laravel-data-breach-registry

Vendor ginkelsoft
Package laravel-data-breach-registry
Short Description A Laravel package that implements the GDPR art. 33/34 personal-data breach register with a hash-chained event log, 72-hour deadline helpers, and CLI for daily monitoring.
License MIT

Keywords laravel avg gdpr compliance audit-log ginkelsoft incident-response breach-registry datalek

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

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.

Please rate this library. Is it a good library?

Example code of ginkelsoft/laravel-data-breach-registry

Informations about the package laravel-data-breach-registry

Ginkelsoft Laravel Data Breach Registry

Overview

Implements the GDPR art. 33 (notification to supervisory authority within 72 hours) and art. 34 (notification to affected subjects when the risk is high) personal-data breach register for a Laravel application.

Two tables work together. breach_register holds the current state of each breach — open, contained, resolved, reported to whom and when. breach_event_log is the append-only, hash-chained audit trail of every state transition, built on the shared HashChain from ginkelsoft/laravel-compliance-core. The register answers "where do we stand?"; the event log answers "how did we get here?", and is the part an auditor will scrutinize.

This is the breach registry member of the GinkelSoft compliance family.

The 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 register — this package
`laravel-compliance-hub`	art. 5(2)	Umbrella

How it works

Register a breach

The 72-hour deadline for notifying the supervisory authority (AP in NL) runs from discoveredAt. The model exposes authorityNotificationDeadline() and isAuthorityNotificationOverdue() for direct use in dashboards.

Update, contain, resolve

Each call atomically updates the register row and appends a hash-chained event. Updates with identical values are no-ops — no event is written when nothing actually changes.

Find the deadlines that matter

CLI

retention:breach:deadlines exits with a non-zero code when there are overdue breaches — perfect for a scheduled job that pages someone when a 72-hour clock is about to expire. The command names keep the retention:breach: prefix for BC with the v1.x monolithic package.

Verify the event log

Or run php artisan compliance:verify from the hub to verify every chain in the family in one shot.

What the log holds

The event log holds only metadata: action names, field diffs, optionally an actor. It never holds personal data — that data lives in the source systems the breach concerns, not in the register.

Compliance notes

GDPR art. 33 — Notification of a personal-data breach to the supervisory authority within 72 hours of becoming aware of it.
GDPR art. 34 — Communication of a personal-data breach to the data subject when the breach is likely to result in a high risk.
GDPR art. 5(2) — Accountability. The event log is the evidence.

This package is not legal advice. Whether a breach requires subject notification (art. 34: "high risk") is your DPIA call, not the package's.

Installation

Then add a secret to .env (shared with the rest of the family):

Gotchas

No notification is automatic. This module records that a breach happened and that you notified — it does NOT actually send the email to the AP or to subjects. The notification itself is a business process you own. Use reportToAuthority / reportToSubjects to mark the moment you completed it.
Severity is your judgement. The package accepts low, medium, high, critical as enum-like values, but does not assess them for you. Whether a breach requires subject notification (art. 34: "high risk") is your DPIA call.
The register is the canonical record, the event log is the proof. Direct Eloquent update() on BreachRegisterEntry is allowed by Laravel but skips the event log; always go through BreachRegistry so the audit trail stays complete.

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-data-breach-registry/issues/new

When opening an issue, please include:

Versions — PHP, Laravel, and the package version (composer show ginkelsoft/laravel-data-breach-registry).
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

All versions of laravel-data-breach-registry with dependencies

PHP Build Version

Package Version

Version v1.0.0 Release 28. May 2026
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of laravel-data-breach-registry from vendor ginkelsoft

Requires php Version ^8.2
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
nesbot/carbon Version ^2.62 || ^3.0
ginkelsoft/laravel-compliance-core Version dev-development

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package ginkelsoft/laravel-data-breach-registry contains the following files

Loading the files please wait ...