- Can I use kevinpapst/adminlte-bundle in a Laravel application?
- No. It is a Symfony bundle that registers through bundles.php, ships a DI Extension class, and relies on Twig templates, Symfony Form/Security/EventDispatcher, KnpMenuBundle, and FOSUserBundle. Composer may resolve the dependency, but there is no service provider, no facade, no Blade views, and no Illuminate contracts, so nothing wires up at runtime. For Laravel you would need a Blade port of AdminLTE rather than this package.
- Does AdminLTEBundle support Laravel 10, 11, or later?
- It supports no Laravel version. The bundle targets Symfony 4/5-era applications and does not even claim or test Symfony 6/7 compatibility. The Laravel version number is irrelevant because the integration layers it depends on, such as Twig, Doctrine, and Symfony Security, do not exist in a Laravel application.
- How do I install kevinpapst/adminlte-bundle with Composer?
- In a Symfony app you run composer require kevinpapst/adminlte-bundle, register the bundle in config/bundles.php, and configure theme options in YAML. Installation inside Laravel will resolve dependencies but produces a non-functional setup. Note that the last release was 2021-11-19 and the repository is now archived.
- Which Symfony versions does kevinpapst/adminlte-bundle support?
- It is built for Symfony 4/5-era applications, compiled with Webpack Encore, and wraps AdminLTE 2 on top of Bootstrap 3 and jQuery. Symfony 6/7 compatibility is not claimed and not tested. Because the repository is archived, no PHP or Symfony version bumps should be expected.
- Is kevinpapst/adminlte-bundle still maintained?
- No. The repository is archived, the last release was 2021-11-19, and it has roughly 210 stars with effectively zero dependents. Archiving means no security patches, no version bumps, and no CVE response. Treat it as a frozen reference implementation rather than a live dependency.
- What license does AdminLTEBundle use?
- GitHub reports NOASSERTION, meaning it could not identify a recognized license for the bundle itself; upstream AdminLTE is MIT, but the bundle's own licensing is unresolved. For anything distributed externally or passing legal review, that ambiguity blocks adoption until counsel clears it. A realistic outcome is unclear provenance, do not ship it.
- How does the AdminLTE bundle menu builder work?
- The bundle provides a menu builder for structured sidebar navigation, typically wired through KnpMenuBundle and rendered by the shipped Twig layouts. You define menu items and the templates output the AdminLTE sidebar markup. In Laravel there is no equivalent in the package's stack, so you would rebuild the menu with a Laravel navigation package and a Blade layout.
- What should I use instead of kevinpapst/adminlte-bundle for a Laravel admin dashboard?
- Pull AdminLTE's static assets from the upstream project and build a Blade layout using @yield and components, or pick a Laravel-native admin starter kit. The bundle's only reusable artifact is the AdminLTE 2 CSS/JS/HTML, which you can get upstream anyway. Reusing the package itself just adds Symfony scaffolding you would have to strip out.
- Can I reuse the AdminLTE Twig templates in Laravel Blade?
- Not directly. Twig syntax, Symfony form themes, and bundle-specific helpers must be translated into Blade directives and Laravel components, which is a port rather than an integration. In practice you reproduce the layout from AdminLTE's static assets, not from the bundle's templates.
- Is AdminLTE 2 with Bootstrap 3 safe for production?
- It carries meaningful risk. Bootstrap 3 is end-of-life with no security patches, the bundle's frozen 2021 npm tree includes jQuery and old Webpack/Encore plugins with known-vulnerable transitive packages, and there is no upgrade path now that the repository is archived. A maintained admin theme built on current Bootstrap or Tailwind is the safer choice.