Weave Code
Admin Crud Laravel Package
mwsimple/admin-crud
A Laravel package for quickly building admin CRUD interfaces, with scaffolding to generate the create, read, update, and delete screens your backend needs. Ideal for developers who want a head start on admin panels without hand-writing every resource.
This bundle admin crud
Frequently asked questions about Admin Crud
- Is mwsimple/admin-crud a Laravel package?
- No. It is published as AdminCrudBundle and uses Symfony and Doctrine idioms such as entities and a base Symfony controller. There is no Laravel service provider, facade, Blade views, or laravel Composer type. Treat it as a Symfony bundle or pattern reference, not an installable Laravel package.
- How do I install mwsimple/admin-crud in Laravel?
- A composer require in a Laravel app would not integrate as expected and could pull Symfony or Doctrine constraints into your dependency graph. Because there is no Laravel service provider or package discovery, no admin routes or Blade views will be registered. The practical path is to study the generator pattern and reimplement it with an Artisan command.
- What Laravel versions does mwsimple/admin-crud support?
- It does not declare Laravel version support at all; it is a Symfony bundle from the PHP 5.6/7.x era. Expect deprecation noise and hard failures on PHP 8.2+ and no compatibility with Laravel 9, 10, or 11. Do not assume Laravel version constraints exist because the package is not Laravel-targeted.
- What does mwsimple/admin-crud actually generate?
- The repository is a code generator that scaffolds a thin CRUD controller per Doctrine entity, with generated controllers inheriting from a shared base class. It also references Symfony forms and Twig-style management views in its original context. It does not generate Eloquent models, Form Requests, API Resources, or Blade views out of the box.
- Can I use mwsimple/admin-crud with Eloquent models?
- Not directly. The package is built around Doctrine entities, not Eloquent models, so you would need to replace entity handling, validation, and persistence with Laravel conventions. A port would map models to Eloquent, Symfony Forms to Form Requests, and Twig templates to Blade. The generator shape is portable; the code is not.
- Is mwsimple/admin-crud maintained or abandoned?
- It is effectively abandoned. The last release was 2019-04-26, roughly seven years without commits, with 20 stars and zero dependents. There is no security policy, no visible CI evidence, and no release cadence to rely on. Maintenance risk is high and concentrated in abandonment.
- What are alternatives for admin CRUD scaffolding in Laravel?
- For Laravel admin CRUD work, mature options include Filament, Laravel Nova, Backpack, and Laravel-admin-style generators. These solve admin UI and resource scaffolding with active maintenance and Laravel-native conventions. They are lower-risk than porting an abandoned Symfony bundle. Choose based on whether you need full admin UI or just controller scaffolding.
- Can I fork and port mwsimple/admin-crud to Laravel?
- Yes, but treat it as a fork-and-port exercise, not a dependency swap. Fork into an internal namespace, run it against your target PHP version, strip Symfony DI and Doctrine coupling, then retarget stubs to Eloquent, Form Requests, API Resources, Blade, and Laravel resource routing. The generator core is small, so this is a days-to-weeks effort rather than a quarter. Name an owner for the fork before starting.
- Is mwsimple/admin-crud safe for production?
- Not as-is. A direct install is at best dead weight and at worst a dependency conflict, and the package has no Laravel runtime integration or security policy. If you port it, publish internally as a dev-only package and keep generated output under your own ownership. Do not put the original bundle into production runtime dependencies.
- How do I test a CRUD generator ported from mwsimple/admin-crud?
- Test the port at the generator boundary: assert that the Artisan command creates the expected controller, routes, Form Request, and views for a sample model. Run generated code in a scratch app against your target Laravel and PHP versions, then add regression tests for stub rendering and naming conventions. Treat generated output as owned code and test it like any other application code.
Weaver
How can I help you explore Laravel packages today?