Weave Code
Crud Generator Laravel Package
mwsimple/crud-generator
A Laravel CRUD generator that scaffolds resource functionality—models, migrations, controllers, and views—from your database or definitions, reducing boilerplate so you can build admin panels and data management screens faster.
CrudGeneratorBundle
Frequently asked questions about Crud Generator
- Is mwsimple/crud-generator actually a Laravel package?
- It is named and packaged as a Symfony bundle, CrudGeneratorBundle, and is built around Symfony and Doctrine conventions rather than Laravel. It does not provide a Laravel service provider, facade, auto-discovery, or Artisan command. Treat it as reference material, not a drop-in Laravel dependency.
- Can I install mwsimple/crud-generator with Composer in a Laravel app?
- Composer may install the package, but installation does not mean integration. There is no Laravel auto-discovery or Artisan wiring, and its Symfony and Doctrine assumptions are likely to conflict with modern Laravel and PHP 8.1+. Validate it only in an isolated spike, not as a runtime dependency.
- Which Laravel versions does mwsimple/crud-generator support?
- No Laravel versions are officially supported. The last release was in 2016, which predates Laravel 10 through 12 and modern PHP 8.x expectations. It targets older Symfony and Doctrine patterns rather than Eloquent, Blade, policies, and Artisan.
- What does mwsimple/crud-generator generate for CRUD screens?
- The project describes CRUD scaffolding such as models, controllers, Blade views, routes, and basic validation, with customizable stubs. However, its templates and metadata conventions come from Symfony and Doctrine rather than Laravel. Any generated output would need porting and code review before use in a Laravel application.
- Does mwsimple/crud-generator integrate with Eloquent and Blade?
- No, there is no native Eloquent or Blade integration. It expects Doctrine entity metadata and Symfony kernel conventions, while Laravel expects Eloquent models, migrations, validation, policies, and Blade, Inertia, or Livewire views. Direct integration would fight the framework rather than speed it up.
- Is mwsimple/crud-generator still maintained?
- Effectively no. The last release was in 2016, it has around 15 stars and zero dependents, and its package score is low. If adopted, your team would own PHP upgrades, dependency patches, template fixes, and security review.
- Is mwsimple/crud-generator safe for production use?
- It is high risk for production. Security posture, test coverage, and compatibility are unknown, and old templates may generate weak validation, missing authorization, inefficient queries, or insecure defaults. Do not use it as production infrastructure without a fork, full review, tests, CI, and a security assessment.
- What are Laravel-native alternatives to mwsimple/crud-generator?
- Laravel Artisan generators, Blueprint, and maintained Laravel CRUD generators cover most scaffolding needs. Evaluate those first because they align with Eloquent, migrations, validation, policies, and Blade. If this package contains unique template logic, fork and port that logic under MIT attribution instead.
- Can I fork mwsimple/crud-generator and port it to Laravel?
- Yes, if its template logic is uniquely valuable. Fork the repository, extract its templates and generation rules, map Doctrine and entity assumptions to Laravel migrations and Eloquent models, preserve MIT attribution, and rewrite it as an internal Artisan command or package. Add tests, CI, static analysis, and clear ownership.
- How should I test mwsimple/crud-generator before adopting it?
- Use an isolated spike rather than your main application. Check PHP 8.x compatibility, Composer dependency conflicts, PSR-4 autoloading, Symfony and Doctrine version constraints, and whether any Laravel service provider or Artisan integration exists. Pilot on one low-risk CRUD module and review generated validation, authorization, pagination, and query efficiency.
Weaver
How can I help you explore Laravel packages today?