Weave Code
Admin Bundle Laravel Package
lin3s/admin-bundle
Lin3S AdminBundle is a Symfony bundle that provides a reusable admin panel foundation for Lin3S projects, bundling common admin UI, routing, and management tooling so teams can bootstrap back-office interfaces quickly.
A lightweight foundation to create an extensible admin panel with ease on top of Symfony
Frequently asked questions about Admin Bundle
- Does lin3s/admin-bundle work with Laravel?
- No. Lin3S AdminBundle is a Symfony bundle built on Twig templating, Symfony routing, and Symfony dependency injection, with no service provider, facade, Blade views, or Eloquent integration. Making it run alongside Laravel would mean booting a Symfony HttpKernel, DependencyInjection container, EventDispatcher, and Router next to Laravel's HTTP layer and bridging two routers and two template engines. That is not a realistic integration path for a production Laravel application.
- How do I install lin3s/admin-bundle with Composer?
- You would run composer require lin3s/admin-bundle inside a Symfony application and then register the bundle in your kernel and add its configuration block. There is no Laravel package discovery, no config/admin.php publish step, and no artisan install command. For Laravel projects the install will technically download code but will not wire anything into the framework.
- Which Laravel and PHP versions does it support?
- None, because the package does not target Laravel at all. Its runtime constraints are Symfony and Twig version coupled and reflect a pre-PHP-7.2 era, so expect composer why-not conflicts on PHP 8.x before you even get to the framework question. Treat the version matrix as a Symfony matrix, not a Laravel one.
- What is the Laravel equivalent of lin3s/admin-bundle for building an admin panel?
- If you want a ready-made Laravel back office, look at packages such as Filament, Nova, Backpack, or Orchid, all of which ship Blade or Livewire views, Eloquent resources, policies, and a service provider. Those give you the same 'layout, navigation, CRUD screens' premise Lin3S AdminBundle offers Symfony, but natively in Laravel. Copying this bundle's Symfony structure into Laravel is more work than starting from a Laravel-native admin package.
- Can I reuse its Doctrine ORM and PDO persistence layer with Eloquent?
- Not directly. The bundle's multi-persistence work supports Doctrine ORM and raw PDO, which shows the authors thought about swappable storage backends, but a PDO adapter is not an Eloquent adapter and there is no ActiveRecord-style integration. It is worth reading as a design pattern if you build your own admin layer natively. It is not something you can point at Eloquent models and expect to work.
- Is lin3s/admin-bundle still maintained?
- Version 0.6.0 shows someone can still build and release the package, which is a mild improvement over a repository frozen in 2017, but a single release after a long gap is not a maintenance commitment. There is no documented security-response process or CVE handling, and ecosystem signals such as stars and dependents were already effectively zero and should be re-verified rather than assumed. Treat it as low-activity at best and unmaintained for planning purposes.
- What changed in version 0.6.0 and is it a breaking change?
- Yes, 0.6.0 is a declared breaking release in the Twig layer: components moved from partial/ to components/, panel-independent Twig components were extracted, and the project explicitly asks consumers to audit their template overrides before upgrading. It also removed jQuery, migrated to ES2015 classes, and bumped the coupled lin3s-front-foundation dependency from v0.5.0 through v0.6.1. Because the package is pre-1.0, semver permits further breaks at any time.
- How do I configure the admin menu and dashboard sections?
- Configuration is done through the standard Symfony bundle configuration tree and Twig template overrides, not through a Laravel config file or a fluent PHP API. You define menus and dashboard sections in bundle config and then customize the provided Twig layout. Because 0.6.0 reorganised the component templates, any existing overrides need to be checked against the new components/ directory.
- Why does it ship a JavaScript and CSS build step if it is a PHP package?
- The bundle owns its own front-end assets, originally jQuery-based and now ES2015 classes, with a parsleyjs import and declared IE11 compatibility that dates the toolchain to roughly 2017 to 2018. That means you would have to graft its asset pipeline onto Laravel Mix or Vite yourself. Coupled front-end dependencies that bumped twice in one release cycle, lin3s-front-foundation v0.5.0 to v0.6.1, are also a supply-chain stability signal for anything you pin.
- Is it safe to run an unmaintained admin panel in production?
- An admin panel is the highest-privilege surface in an application, handling authentication, routing, and rendering, so unmaintained admin code carries disproportionate risk. This bundle has no visible security-response process and its runtime assumptions are stale, which means you own any vulnerability you inherit. For a Laravel application the safer decision is to use a maintained Laravel-native admin package rather than vendoring or forking this one.
Weaver
How can I help you explore Laravel packages today?