Audit — Laravel Smells

When to use

• The user wants an audit of an existing Laravel application — find facade abuse, missing FormRequests, sync queues in production, leaked .env secrets, or N+1 queries.
• The user wants to find N+1 query problems, eager-loading gaps, or a sync queue driver running in production across an existing Laravel codebase.
• The user wants to check a Laravel app for controllers that validate inline instead of using FormRequests, or for secrets and credentials leaked into a committed .env file.

When NOT to use