- How do I install and configure Auditor Bundle in a Laravel application?
- Add the package with Composer and let Laravel package discovery register its service provider. Publish the configuration and run the package migrations to create the audit table. Then configure which models and events should be audited and confirm that only one audit service provider is registered.
- Does Auditor Bundle work with Laravel 10 and Laravel 11?
- The package is built for standard Laravel architecture, but you should verify the exact PHP and Laravel version constraints in its composer.json before upgrading. The TPM assessment flags version constraints as part of the compatibility surface, especially after the 5.2.6 vendor re-point. Test in a branch against your app's Laravel version and a production-shaped database before rolling it out.
- How does Auditor Bundle record who changed what and when?
- It hooks into Eloquent model events or observers and writes an audit row when audited models are changed, depending on configuration. Each record captures the affected model, the changed attributes, the acting user, and a timestamp. That gives you a searchable history for debugging, accountability, and compliance reviews.
- Can I audit model create, update, and delete events automatically?
- Yes, the package is designed to hook into Eloquent-level events, so model saves and deletes can generate audit entries without custom code in every controller. You configure the audited models and event set in the package config. Verify each model after install, including soft deletes, because audit integrity depends on those hooks firing consistently.
- How do I exclude sensitive attributes from audit logs?
- Auditor Bundle lets you control the audited model set and attribute handling through configuration, so you can redact or exclude sensitive fields before they are persisted. Treat redaction as a compliance control: confirm the rule in a test environment and inspect actual audit rows, not just config. The 5.2.6 vendor re-point is also a good time to re-verify that upstream changes did not alter redaction or retention behavior.
- What database schema and migrations does Auditor Bundle add?
- It typically adds an audits table through publishable migrations, with columns for the audited model, event, changed values, user, and timestamps. Review the exact schema in the package migrations before running them. If you are upgrading from an older package reference, snapshot the current schema and compare it after the change to confirm backward compatibility.
- Is Auditor Bundle suitable for SOC 2, ISO 27001, or GDPR audit trails?
- It can support accountability and traceability controls by keeping a searchable history of model changes and user actions, but the package alone does not make you compliant. You still need retention policies, access controls, integrity protections, and evidence that audit writes are reliable. Because audit tables are often used as compliance evidence, document the 5.2.6 dependency re-point and verify that redaction and soft-delete behavior did not change.
- What changed in Auditor Bundle 5.2.6 and do I need to update composer.json?
- Patch 5.2.6 changes package references to point at tejadong/auditor, so the main application change is a Composer coordinate update rather than a code-path rewrite. Update composer.json, refresh the lockfile, and reconcile CI caches and any approved-vendor allowlists. Run composer update for the package in a branch and verify a single service provider and a clean migration on a production-shaped database.
- How do I avoid duplicate service providers or observers after switching to tejadong/auditor?
- Check composer.lock and composer show to confirm only one audit package is resolved, because having both the old and new references can register two providers or duplicate observers. Clear config and package discovery caches, then inspect the registered providers and the audit table writes. Run create, update, and delete tests on representative models and compare the audit rows against a pre-change baseline.
- How should I test Auditor Bundle in a Laravel test suite?
- Use a test database and run the package migrations, then perform create, update, and delete actions on audited models and assert the expected audit rows. Cover user attribution, redaction, soft deletes, and console or queued actions if your app uses them. Keep a baseline of audit output before the vendor re-point so you can diff behavior after upgrading.