Weave Code
Loggable Bundle Laravel Package
ibrows/loggable-bundle
Symfony bundle that automatically logs changes to Doctrine entities, tracking who created, updated, or deleted records. It hooks into Doctrine listeners and the Symfony event system to build an auditable history of your application's data without repetitive logging code in every service.
At a glance
Frequently asked questions about Loggable Bundle
- Can I use ibrows/loggable-bundle in a Laravel application?
- No. ibrows/loggable-bundle is a Symfony bundle that integrates through Symfony's dependency-injection container and Doctrine ORM listeners, while Laravel uses Eloquent. There is no native seam for it to attach to in a Laravel app, so it cannot be installed and configured as a normal Composer dependency. Treat it as a reference implementation for the diff-and-log pattern rather than a package you adopt.
- How does ibrows/loggable-bundle log Doctrine entity changes?
- It registers Doctrine flush lifecycle listeners that capture insert, update, and delete operations on configured entities. Each log entry stores the affected fields, previous and new values, a timestamp, and optional user context. Retrieval exposes an entity's historical versions without adding logging code to domain services.
- What is the Laravel alternative to ibrows/loggable-bundle?
- For Laravel, use owen-it/laravel-auditing for field-level model auditing with before and after payloads, or spatie/laravel-activitylog for broader activity logging. A small set of Eloquent observers can also reproduce the core pattern in roughly 100 to 300 lines. None of these require Doctrine.
- How do I configure which entities and fields are audited in ibrows/loggable-bundle?
- In a Symfony app you install it with Composer, enable the bundle, and configure the list of logged entities plus ignored fields. You can optionally wire user attribution so each change entry records an actor. In Laravel there is no equivalent configuration because the bundle is not Laravel-native.
- Which Laravel versions are supported by ibrows/loggable-bundle?
- None. The package is built for Symfony and Doctrine, so it has no Laravel version constraints or support matrix. Laravel compatibility is not a meaningful question for this codebase. If you need Laravel support, evaluate laravel-auditing or spatie/laravel-activitylog instead.
- How do I test audit logging for Eloquent models in Laravel?
- Create or update an Eloquent model inside a RefreshDatabase or DatabaseTransactions test, then assert that the audit table contains the expected event, actor, field, old value, new value, and timestamp. Use model factories to make the setup repeatable. Also test ignored fields and deleted records so the log payload matches your compliance rules.
- Is ibrows/loggable-bundle maintained and safe for production use?
- The repository shows zero stars, zero dependents, and no adoption evidence, which points to high supply-chain and abandonment risk. That does not mean the pattern is bad, but it does mean you should not rely on it as a maintained production dependency. Fork the logic or reimplement it natively if you want the behavior.
- How do I log field-level before and after values for Laravel models?
- Use owen-it/laravel-auditing or a custom Eloquent observer that reads getOriginal() and getChanges() during saved and deleted events. Store the model type, model id, event, actor id, changed field, old value, new value, and timestamp in an append-only table. Keep redaction and allow-listing in the design so PII is not duplicated blindly.
- What are the best alternatives to ibrows/loggable-bundle for Symfony Doctrine auditing?
- For Symfony and Doctrine, evaluate Gedmo Loggable or a maintained Doctrine audit bundle, or write a focused EntityListener or EventSubscriber. Those options have more adoption and documentation than ibrows/loggable-bundle. The hand-written listener is often enough for a narrow audit requirement.
- Does ibrows/loggable-bundle meet compliance and PII requirements for audit logging?
- The bundle copies field values into a separate log entity, which can silently duplicate personal data, and it does not by itself provide tamper-evidence, retention windows, or guaranteed pre-commit writes. Treat PII redaction and field allow-listing as design requirements from day one. If regulatory compliance is in scope, build a purpose-specific audit design rather than adopting a generic CRUD log package.
Weaver
How can I help you explore Laravel packages today?