Weave Code
Audit Logger Bundle Laravel Package
minvws/audit-logger-bundle
A Symfony bundle for structured audit logging of security-relevant events. It records who did what and when, with configurable storage and integration points, helping PHP teams meet compliance, traceability, and accountability requirements.
Generic audit logger bundle for symfony
Frequently asked questions about Audit Logger Bundle
- Does minvws/audit-logger-bundle work with Laravel out of the box?
- No. The package is a Symfony bundle with config/bundles.php registration, compiler passes, a configuration tree, and kernel event subscribers, so it has no Laravel service provider or Eloquent integration. You can use it in Laravel only by wrapping the audit-writing core or treating it as a specification and reimplementing the write path. The 1.1.0 release adds AuditLoggerInterface registration but still binds it through Symfony's container.
- How do I install minvws/audit-logger-bundle with Composer?
- Run composer require minvws/audit-logger-bundle and, in Symfony, register the bundle in config/bundles.php. There is no Laravel auto-discovery or package manifest, so a Laravel install will not wire services automatically. Verify the released tag and the 2026-04-14 date against the tag history before pinning.
- What is AuditLoggerInterface and why does it matter?
- AuditLoggerInterface is the named contract for the audit-writing core, and as of 1.1.0 it is registered in the bundle's dependency injection configuration. That gives consumers a seam to inspect, but the interface is Symfony-namespaced and is not exposed through a PSR-11 factory. For Laravel, it is a starting point for extraction, not a drop-in contract.
- Is the audit log tamper-evident and append-only?
- The overview claims a tamper-evident, immutable format, but the decisive implementation details are not established in the release notes. You need to confirm whether storage uses append-only rows, hash chaining, a WORM backend, or plain database rows. Treat the claim as a requirement to verify in code and in your compliance review.
- Does minvws/audit-logger-bundle support PSR-3 logging channels?
- Yes, the package describes PSR-3 compatible logging with a dedicated audit channel and structured context for actor, action, resource, and outcome. That is useful for forwarding entries into Monolog or a Laravel log stack. The Symfony-specific part is the wiring around the logger, not the PSR-3 concept.
- How do I configure audit event retention and filtering?
- Retention and filtering are configured through the bundle's configuration tree in Symfony. In a Laravel adaptation, that would be re-hosted as config/audit-logger.php and bound through a service provider. Check the exact config keys before designing your own because renames are not documented in the 1.1.0 changelog.
- Can I inject a custom audit logger implementation?
- The 1.1.0 change registers AuditLoggerInterface in the bundle's DI configuration, which suggests a service alias you may be able to override. It is not confirmed whether the binding is overridable through bundle config or hard-wired to the default implementation. Read the service definition and compiler pass to confirm before relying on it.
- What license does minvws/audit-logger-bundle use, and what are the obligations?
- The package is EUPL-1.2, a copyleft license whose obligations trigger on distribution rather than network use. Internal SaaS use is likely fine, but on-premise delivery or distributing a modified bundle requires source disclosure and legal sign-off. Confirm with counsel before shipping it to customers.
- Is minvws/audit-logger-bundle actively maintained?
- Adoption signals are weak: 0 stars, 0 dependents, single-vendor government provenance, and no visible issue triage community. Release 1.1.0 is a scoped, reviewed, merged PR from a new contributor, which is a small positive for cadence but not a support commitment. Two releases and two contributors do not establish a support window for the 1.x line.
- What are the alternatives for audit logging in Laravel?
- Laravel teams commonly use owen-it/laravel-auditing or spatie/laravel-activitylog for model and activity trails, or a custom PSR-3 channel with structured context. If you need the minvws schema or compliance semantics, reimplement the write path natively with Eloquent and a service provider. Use the bundle as a specification rather than a runtime dependency when Symfony coupling is unacceptable.
Weaver
How can I help you explore Laravel packages today?