lc:spatie-permissions-audit

Auditing spatie/laravel-permission involves cross-referencing defined permissions in seeders and migrations against actual usage in Blade, controllers, and middleware. This detects undefined permissions, unused roles, and guard mismatches that cause silent authorization failures and expose sensitive endpoints.

Silent authorization failures occur due to undefined permissions, incorrect middleware aliases, and stale cache issues. These inconsistencies happen when defined permissions in seeders do not match actual usage in controllers, Blade templates, and middleware configurations across the application lifecycle.

The best way to find unused roles and dead code is to perform a comprehensive audit that cross-references codebase references, database definitions, and middleware configurations. This detects undefined permissions, unused roles, and security misconfigurations within your Laravel application's authorization setup.

Yes, you can automatically fix guard mismatches and unprotected routes using automated remediation techniques. This approach offers safe, confirmation-based fixes for missing permissions, incorrect middleware aliases, and stale cache issues while validating guard consistency across your application.

To ensure proper registration of authorization aliases, you must validate guard consistency and analyze middleware configurations across the application lifecycle. This verifies that defined permissions are correctly registered and prevents silent authorization failures in your Laravel application.