Laravel Development · page 6

Validate signed URL structure and expiration behavior using supplied application context.

Flag relationship access patterns that may cause excessive database queries.

Find models without factories or with incomplete factory definitions.

Identify transaction boundaries and potential partial-write risks.

Flag raw SQL statements that need injection-safety review.

Compare application upload validation with web server and PHP limits.

Identify critical sections that may require distributed locks.

Review session driver, lifetime, cookie security, and storage configuration.

Identify relationships and queries that may mishandle soft-deleted records.

Verify command exit codes, output formats, and failure handling.

Check common PHP, Composer, environment file, and application prerequisites.

Paste a composer.json file to validate structure, missing sections, and risky settings.

Enter a version constraint to get a plain-English explanation of matched release ranges.

Paste composer.json autoload blocks to report namespace-to-path mismatches and missing mappings.

Paste composer.json scripts to see which script fires on each composer event lifecycle hook.

Paste two composer.lock files to summarize added, removed, and changed package versions.

Paste namespaces and class files to flag duplicate class declarations across classmap paths.

Enter your project license to see a matrix of which package licenses are safe to depend on.

Paste required packages and versions to get a recommended minimum-stability and prefer-stable setting.

List packages and local patches to generate a patches.json structure with apply order.

Paste composer.json require-dev to get a checklist of dev tools to drop for lean CI installs.

Enter a package list and repo URLs to generate a private Satis repository config JSON.

Enter target PHP and extension versions to get a platform config snippet that locks deployments.

Describe changes as fix, feature, or breaking to get the correct SemVer release increment.