- What does achillesp/laravel-crud-forms do?
- achillesp/laravel-crud-forms is a Laravel package for quickly scaffolding CRUD forms and interfaces around Eloquent models. It generates create, edit, and delete flows using reusable Blade form components and validation, which reduces boilerplate when building admin panels and management screens. It is aimed at applications that follow conventional Laravel structure.
- Which Laravel and PHP versions are supported?
- Based on the available release information, one release line supports Laravel 11, 12, and 13. The PHP floor is 8.2, but Laravel 13 requires PHP 8.3 or newer. Verify your CI images, Docker base images, and local development containers meet those requirements before adopting it.
- How do I install laravel-crud-forms?
- Install it with Composer using composer require achillesp/laravel-crud-forms. Then run php artisan vendor:publish if you need to publish its configuration or assets. Laravel package auto-discovery should handle service provider registration, but confirm the README for any additional setup steps.
- Does it support Laravel 13?
- Yes, the package's single release line is reported to cover Laravel 11, 12, and 13. Running it on Laravel 13 requires PHP 8.3 or newer across your runtime and CI environments. Treat the Laravel 13 upgrade and the package upgrade as separate changes so you can isolate failures.
- What changed between version 8.0 and 9.0?
- The release notes reportedly describe only added framework support, so the 8.0 to 9.0 diff is the central unknown. Because it is a semver-major release, review the full diff for renamed methods, changed config keys, altered generated stubs, or dropped features. Do not assume the upgrade is purely additive without checking the package's published config, templates, and public API.
- Does it respect Laravel policies and gates?
- That is a key question to validate rather than assume. The package sits on top of Laravel conventions, but you should confirm in the code and documentation whether it respects your policies and gates or imposes its own authorization behavior. Add feature tests that prove unauthorized users cannot create, edit, or delete records through the generated forms.
- Does it generate code once or regenerate it?
- The available information does not state whether generated CRUD forms are scaffold-once files you own or artifacts that can be regenerated. This distinction determines your blast radius when the package is upgraded or customized. Confirm the intended workflow in the README and test a regeneration on a throwaway branch before relying on it.
- Is it safe to use in production?
- Forms are the input boundary, so treat this package as security-sensitive. It is a single-maintainer project without indicated commercial backing, so review its disclosure policy, release cadence, and history of security patches. Pin an exact version during evaluation, keep the previous lockfile for rollback, and cover validation, mass assignment, CSRF, and output escaping in tests.
- How should I test generated CRUD forms?
- Write feature tests that submit valid and invalid payloads to the generated create and edit endpoints. Assert that validation errors appear, unauthorized users are blocked, mass-assignment fields are guarded, and CSRF protection remains enabled. Also test the delete flow and confirm that success and failure paths redirect or respond as expected.
- What are alternatives to this package?
- Alternatives include writing your own Blade form components, using Laravel's validation and resource controllers directly, or adopting a broader admin panel framework such as Filament, Laravel Nova, or Backpack. This package is narrower: it scaffolds CRUD forms around Eloquent models. Choose it when you want lightweight scaffolding without committing to a full admin framework.