Weave Code
Admin Crud Extensions Bundle Laravel Package
lin3s/admin-crud-extensions-bundle
Lin3s AdminCrudExtensionsBundle extends Symfony admin CRUD workflows with reusable helpers and configuration for lists, forms, filters, and actions, reducing boilerplate and helping teams build consistent back-office screens faster.
Lin3s Admin CRUD Extensions Bundle is a Symfony bundle that adds reusable extensions on top of a simple CRUD admin layer, reducing boilerplate when building back-office interfaces. It provides shared services, traits and helpers so common admin actions can be composed consistently across resources.
- Drop-in CRUD extensions for Symfony admin controllers
- Reusable services and traits to cut boilerplate
- Consistent structure for list, create, edit and delete flows
- Easy integration with existing Lin3s admin projects
- PSR-compatible, Composer-installable package
Frequently asked questions about Admin Crud Extensions Bundle
- Is lin3s/admin-crud-extensions-bundle a Laravel package?
- No. It is a Symfony bundle and ships no Laravel service provider, config publish tag, or Laravel contracts, so there is no supported integration path in a Laravel application. Evaluating it against Laravel stops at stack mismatch; you would have to port the source to use it.
- What does LIN3S AdminCRUDExtensionsBundle actually do?
- It layers extra CRUD functionality onto the LIN3S AdminCrud bundle, adding reusable extensions for building and customizing admin panels. It is a thin extension layer, not a standalone admin package. Its value depends entirely on already running lin3s/admin and staying compatible with that bundle's internal APIs.
- How do I install lin3s/admin-crud-extensions-bundle?
- You install it with Composer alongside the base AdminCrud bundle, but expect dependency resolution problems on modern Symfony. The last release was in October 2017, targeting the Symfony 3.x and PHP 7.0–7.1 era, and its constraints will likely conflict with current symfony/* and doctrine/* majors. Only attempt this inside a legacy Symfony app that already uses LIN3S Admin.
- Can I use this bundle with Laravel 10 or 11?
- No. The package is a Symfony bundle, not a Laravel package, and it provides no service provider, facade, config file, or Laravel-specific integration. There is no version of Laravel it supports because Laravel support was never implemented. Using it would require porting the code yourself.
- Which Symfony and PHP versions does this bundle support?
- The last tagged release is from 2017-10-06, which places it in the Symfony 3.x and PHP 7.0–7.1 era. There have been no releases since then, so there is no semver signal for newer Symfony or PHP versions. Modern Symfony 5.4, 6.x, and 7.x removed or deprecated much of what bundles from that period rely on.
- Do I need lin3s/admin installed to use these CRUD extensions?
- Yes. The bundle is a second-order dependency that extends lin3s/admin and assumes its Doctrine entity conventions, routing, and templating assumptions. Without the parent bundle it has no independent value. Adopting it means adopting the entire LIN3S admin stack and its release cadence.
- Is lin3s/admin-crud-extensions-bundle maintained or abandoned?
- It appears abandoned. The last release was in October 2017, and the repository shows no recent commits, zero stars, and zero dependents. There is no observable consumer base, no documentation of note, and no issue history to consult. You should treat the master branch as the only source of truth and plan to own any fork.
- What are good alternatives to this bundle for building admin panels?
- For Symfony, EasyAdmin is the closest actively maintained conceptual match, and SonataAdmin is a heavier but established option. For Laravel, use Filament, Nova, or Backpack rather than trying to adapt a Symfony bundle. Reimplementing only the CRUD behavior you actually use is often cheaper than maintaining an abandoned fork.
- How should I test or evaluate this bundle before adopting it?
- Start by checking whether you already run lin3s/admin in production; if not, stop, because the bundle has no standalone value. Then verify whether its Composer constraints can be satisfied by the PHP and Symfony versions you must support over the next 12 months. Expect composer require to fail resolution before you write any code, and review the source directly since there are no meaningful tests or docs.
- What are the production risks of depending on this package?
- The risks are high and multi-dimensional: abandonment, transitive dependency exposure through the parent bundle's Doctrine and Symfony pins, and a lack of docs, tests, or issue history. An unmaintained admin bundle often drags in unpatched PHP libraries that show up in SCA scans. If you fork it, assign an owner and an exit trigger, and budget permanent maintenance.
Weaver
How can I help you explore Laravel packages today?