Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Action Logger Bundle

Action Logger Bundle Laravel Package

gepur-it/action-logger-bundle

A Symfony bundle for logging user and system actions into a structured audit trail. It helps capture activity and events with configurable logging, making it easier to review history, debug issues, and support compliance requirements.

View on GitHub
Deep Wiki
Context7

Action logger bundle

Frequently asked questions about Action Logger Bundle
Is gepur-it/action-logger-bundle a Laravel package?
No. It is a Symfony bundle built around Symfony dependency injection, Symfony EventDispatcher subscribers, and Doctrine lifecycle listeners. It does not provide a Laravel service provider, facade, config publish target, or package auto-discovery. Treat it as a design reference for Laravel, not a drop-in Laravel audit log package.
Can I install gepur-it/action-logger-bundle in a Laravel application?
Composer installation does not give you a working Laravel integration. The package expects Symfony bundle wiring and Doctrine event listeners, not Laravel service providers, Eloquent model observers, or Laravel events. You would need a fork or a native reimplementation to use the pattern in Laravel.
What does this bundle actually log?
It records user actions and entity changes into a structured audit log. The focus is entity or state-delta tracking for create, update, and delete operations, including field-level before and after values. It stores the responsible user, request context, and timestamp alongside the change.
Does it capture before and after field changes for Doctrine entities?
Yes. It hooks into Doctrine lifecycle events and stores field-level before and after diffs with the acting user and timestamp. It also supports configurable entity exclusions and ignored fields. This makes it closer to an entity audit trail than a raw request log.
What storage backends does gepur-it/action-logger-bundle support?
The bundle lists PSR-3 logger and database storage adapters. The persistence appears repository-pattern based and likely Doctrine ORM or DBAL oriented. That matters for Laravel because it is not an Eloquent-backed audit table by default.
How does it intercept create, update, and delete actions?
It uses Doctrine event listeners for entity lifecycle events. That is not the same as Laravel model observers, Laravel events, or middleware. A Laravel port would need to recreate those interception points with observers and middleware for actor and request context.
Is this bundle suitable for compliance and PII audit trails?
It can support compliance and accountability use cases because it records field-level changes to customer records. That also raises PII handling concerns, including redaction, retention windows, and right-to-erasure requirements. A customer-data audit trail needs an owner and clear policies, not just a logging utility.
How do I configure entity exclusions and ignored fields?
The bundle provides configurable entity exclusions and ignored fields in its Symfony bundle configuration. In Laravel there is no config publish target or service provider integration for that configuration. A port would need a Laravel config file and wiring through a service provider.
Is it maintained and safe for Laravel production use?
The v5.0.6 line suggests the package has had multiple majors and patches, so it is not a single abandoned release. However, there is no evidence of Laravel support, modern PHP 8.3 or 8.4 constraint hygiene, dependents, or production battle-testing. Technical risk remains high, especially if stale transitive constraints block a Laravel upgrade.
What are Laravel alternatives and how should I test a port?
For Laravel, owen-it/laravel-auditing is closer to the Eloquent model-audit use case. A native implementation would use model observers to capture diffs, middleware to attach actor and request context, and an Eloquent-backed audit table. Test it with feature tests that assert log rows contain before and after values, the responsible user, request context, and timestamps. Use database transactions in tests so audit records do not leak between cases.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect
youbar/easy-crud
c-point-labs/laravel-hostyourai
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo