eloquent-audit

To find and fix Laravel Eloquent N+1 query problems, this audit scans controllers, Livewire components, and services for eager loading opportunities. It flags inefficient relationship access and reports findings with actionable refactoring steps and configurable thresholds.

Auditing Eloquent models for missing casts and mass-assignment risks involves scanning your models to flag unsafe query patterns and data integrity issues. This process produces a consolidated findings report with concrete recommendations to improve data integrity and runtime performance.

Yes, you can scan Laravel API resources and repositories for Eloquent query optimization. The audit evaluates serialization and query patterns across your codebase, identifying unnecessary data loading and providing best-practice guidance to improve performance and correctness.

Yes, the Eloquent audit enforces scope by excluding vendor, node_modules, and storage directories when scanning PHP source files. This ensures the analysis targets your application code in controllers, models, migrations, and tests without processing external dependencies.

Configuring N+1 detection thresholds for a Laravel codebase audit allows you to set limits for query optimization analysis. The audit applies these thresholds while scanning your PHP source files, reporting only the Eloquent usage patterns that exceed your defined configuration.