laraveldaily-production-readiness-audit

A Laravel production-readiness audit scans repository files locally to identify hidden secrets, debug code, and configuration issues. It returns findings categorized as critical, warning, or note without requiring environment variables.

Risky env() usage in a Laravel application occurs when env() is called outside allowed configuration files. The audit flags these calls because they bypass configuration caching and can cause runtime failures in production environments.

To find committed debug statements in a Laravel project, you scan the PHP files for dd, dump, var_dump, print_r, phpinfo, exit, and die usages. The audit identifies these high-confidence code patterns and reports them as production-readiness risks.

A Laravel security audit does not require environment variables to detect hard-coded API keys. The skill operates locally by parsing repository files directly, focusing on high-confidence code patterns and configuration issues without relying on runtime environment data.

Yes, the audit can detect unsafe seed data and missing lockfiles. It also highlights asset build mismatches and committed .env files, grouping all these findings into a comprehensive report with critical, warning, and note sections.