Weave Code
Activity Logger Bundle Laravel Package
modera/activity-logger-bundle
A Laravel bundle for recording user and system activity, giving you an audit trail of events across your application. Log actions, review histories, and track what changed and who changed it. Useful for compliance, debugging, and monitoring workflows.
[READ-ONLY] Allows to track user actions from your code by providing Psr's LoggerInterface compatible logger.
Frequently asked questions about Activity Logger Bundle
- Is modera/activity-logger-bundle a Laravel package?
- No. Despite being described as a Laravel bundle, it is a Symfony bundle built around Symfony's DI container, EventDispatcher, and Doctrine ORM listeners. There is no Laravel service provider, facade, config publish stub, or package discovery support. Adopting it in Laravel would mean porting the listener logic yourself, so it is not a drop-in fit.
- How do I install modera/activity-logger-bundle with Composer in a Laravel app?
- You can run composer require modera/activity-logger-bundle, but nothing will auto-register in Laravel because there is no service provider. The package targets Symfony 2.3-3.x and the PHP 5.5-7.0 era, so dependency resolution will likely fail on a modern Laravel stack. Even if it installs, there is no config to publish and no Laravel integration to wire up.
- Which Laravel versions does modera/activity-logger-bundle support?
- None officially. The bundle predates modern Laravel and has no adapter for Laravel's container, events, or Eloquent. It was last released in 2016 and targets Symfony, not Laravel. Laravel 8, 9, 10, and 11 are not supported.
- Is modera/activity-logger-bundle still maintained?
- No. The last release was 2016-06-10, the repository has roughly 4 stars and zero dependents, and there has been no maintainer activity for about nine years. There is no CVE response process and no production user base to lean on. Treat it as abandoned rather than a dependency.
- What should I use instead of modera/activity-logger-bundle in Laravel?
- Use spatie/laravel-activitylog for human-readable activity feeds, owen-it/laravel-auditing for before/after audit trails, or Eloquent observers with a custom append-only table for low-level change capture. All three are actively maintained and Laravel-native. The functional gap versus Modera's bundle is small, while the operational gap is enormous.
- Can I use modera/activity-logger-bundle for a compliance audit trail?
- It is not advisable. Audit logging is compliance-adjacent, and running unpatched 2016 code in the audit path is a governance finding waiting to happen. Choose a maintained package with active security response, plus explicit retention, immutability, and PII controls. Also confirm whether your requirement is compliance auditing, a user-facing feed, or debugging telemetry, because each has different constraints.
- Why won't modera/activity-logger-bundle run on PHP 8 or Laravel 10?
- Its constraints target PHP 5.5-7.0 and Symfony 2.3-3.x, with Doctrine ORM listener APIs from that era. Transitive dependencies pinned to 2016 versions commonly hit reserved words, removed functions like each(), and nullable or return-type conflicts. Composer will likely refuse the install, and the code would fatal at runtime even if it did install.
- What does modera/activity-logger-bundle actually do?
- It provides a PSR-3 LoggerInterface-compatible logger that records user actions into an activity log, typically wired through Doctrine listeners and Symfony's event dispatcher. The result is an audit trail of who changed what across your application. Functionally it overlaps with spatie/laravel-activitylog, but it is Symfony-specific and dated.
- How hard is it to port modera/activity-logger-bundle to Laravel?
- High effort. You would replace the Symfony DI extension and CompilerPass with a Laravel service provider, map the Symfony EventDispatcher to Laravel events, and rewrite Doctrine listeners against Eloquent. At that point you have built a custom package, so it is worth comparing against existing Laravel libraries first. For most teams, building on a maintained package is cheaper and safer.
- How do I migrate an existing Modera activity_log table into a Laravel app?
- Capture the existing DDL and row shape first, and let your new schema be driven by that rather than by the new library. Run a dual-write window where the legacy Symfony app emits events via a queue or message bus into the new store instead of sharing a database connection. Backfill and verify reads, then cut over read paths and retire the bundle. This preserves history without requiring the stale bundle to run on modern PHP.
Weaver
How can I help you explore Laravel packages today?