laraveldaily-structure-audit

Scanning PHP source files detects inline validation, fat controllers, hard-coded strings, and env misuse, excluding vendor, node_modules, and storage directories. It produces a structured refactoring report with actionable suggestions following Laravel best practices.

Fat controllers in Laravel are methods exceeding roughly twenty lines or containing multiple responsibilities. Scanning controller files highlights these methods and recommends extracting services or action classes to improve code maintainability.

Using the env function outside config files in Laravel causes production bugs because env returns null after configuration caching. Env misuse detection catches these calls to prevent configuration failures in production.

Detecting duplicate logic and hard-coded strings involves scanning Laravel controllers for repeated code blocks and literal role or status values. The audit recommends extracting shared scopes or services and replacing strings with PHP Enums.

Yes, you can audit a Laravel application by specifying its directory path. The audit scans PHP source files within that location to identify architectural issues and outputs a concise refactoring report with actionable suggestions.

Refactoring inline validation in Laravel involves extracting complex validation logic from controllers into dedicated Form Request classes. The audit detects large inline validation blocks and recommends this extraction for better code organization.