- What does rezaamini-ir/laravel-tracker do?
- Laravel Tracker is a lightweight package for monitoring activity in a Laravel application. It records tracked events and stores them for review, giving you a simple way to keep an audit trail and better understand what is happening inside your app. It is aimed at conventional Laravel applications that want model-level activity tracking without building a full audit system from scratch.
- Which Laravel and PHP versions does laravel-tracker support?
- The public context does not clearly establish which Laravel and PHP versions are supported. The package had a last release in January 2021, so you should inspect its composer.json constraints and test against your target runtime before installing it. A modern Laravel 10 or Laravel 11 application should assume a fork or replacement may be required.
- Is laravel-tracker compatible with Laravel 10 or Laravel 11?
- There is no evidence in the provided context that laravel-tracker has modern Laravel 10 or Laravel 11 compatibility testing. Its last release was in January 2021, and it has very low community usage with only 12 stars. Treat it as a legacy stopgap or reference implementation rather than a strategic dependency for current Laravel versions.
- Is rezaamini-ir/laravel-tracker still maintained?
- The package appears to carry high abandonment risk based on the last release date in January 2021 and limited production adoption evidence. There is little indication of ongoing compatibility testing, security updates, or active maintenance. For long-lived systems, prefer a maintained audit-log capability or a small internal implementation owned by your team.
- Which Eloquent events does laravel-tracker capture?
- The provided overview does not specify exactly which Eloquent events are captured. You should inspect the package source and tests to confirm whether it handles created, updated, deleted, restored, force-deleted, and custom events. This matters because incomplete event coverage can leave gaps in your audit trail.
- Does laravel-tracker store old and new values, user IDs, IP addresses, or user agents?
- The public context does not confirm what is stored per change. Before adopting it, inspect the schema and tracking logic for old and new values, user ID, request context, IP address, user agent, and tenant ID. Also verify how sensitive attributes, PII, and large payloads are handled, because built-in redaction and retention policies may be missing.
- Can laravel-tracker failures block model writes or roll back transactions?
- This depends on whether tracking runs synchronously inside the request transaction. If it does, a tracking insert failure could affect business writes or rollbacks, so test failure behavior explicitly. Include tests for tracking insert failure, transaction rollback, queue failure, and observer recursion before using it in production.
- Does laravel-tracker support soft deletes, UUIDs, JSON casts, and multi-tenancy?
- Support for soft deletes, UUID or ULID keys, casts, JSON columns, and multi-tenancy is not established in the provided context. The package may assume an integer primary key or a specific user resolver. Validate these cases with representative models in a sandbox before integrating it into a real application.
- How should I install and integrate laravel-tracker in a legacy Laravel app?
- Composer installation may work only if the package constraints match your target Laravel and PHP versions. For a legacy stopgap, fork it into an internal namespace, pin the version, add compatibility tests, and wrap access behind an internal AuditLogger or ModelTracker interface. Build a proof of concept on representative models and plan an exit path to a maintained package or internal observer-based audit table.
- What are alternatives to laravel-tracker for audit logging in Laravel?
- Consider a maintained audit-log package or a small internal observer-based audit table owned by your team. For compliance-grade requirements, you also need immutability, retention, PII redaction, and tamper-evidence controls that this package may not provide. Given its age and low usage, laravel-tracker is best treated as a legacy stopgap or reference implementation rather than a long-term dependency.