- Does labs64/laravel-boilerplate work with Laravel 10 or Laravel 11?
- Most likely not without significant work. The last release was 2020-04-01, so its Composer constraints target legacy Laravel and PHP versions, and it is expected to conflict with Laravel 10 or 11 and PHP 8.1+. Audit composer.json and run a proof-of-concept on your target runtime before committing to it.
- How do I install labs64/laravel-boilerplate?
- Treat it as a starter kit rather than a package: clone or fork the repository, run composer install, configure your .env file, and run migrations. You cannot cleanly composer require it into an existing Laravel application because it ships a full application skeleton and dependency graph. Plan to own the fork and its upgrades from day one.
- What Laravel and PHP versions does this boilerplate require?
- The 2020 release date implies legacy constraints, typically PHP 7.x-era and an older Laravel release. The exact versions should be verified in the repository's composer.json before any evaluation. Expect to upgrade Laravel, PHP, and frontend tooling if you adopt it for a new project.
- Is labs64/laravel-boilerplate still maintained?
- No, it appears unmaintained, with its last release in April 2020 and community-only support. GitHub issues may be stale, and there are no upstream security patches or vendor SLAs. If you fork it, your team owns dependency CVEs, Laravel upgrades, theme fixes, and compatibility work.
- What features are included in this Laravel starter kit?
- It bundles authentication, user, role and permission management, themes, settings, activity logs, API support, and an extensible admin foundation. These are aimed at greenfield, server-rendered back-office applications built with Blade and Bootstrap. The scaffolding can save initial setup time, but the UI layer is dated and needs review.
- Can I add labs64/laravel-boilerplate to an existing Laravel application?
- Not cleanly. It is a monolithic skeleton with its own conventions, routes, assets, and dependency graph, so integrating it into a mature product usually causes conflicts. A safer approach is to extract auth and RBAC patterns or use it as a reference implementation, then rebuild the UI with maintained packages.
- Is labs64/laravel-boilerplate safe to use in production?
- It carries high technical and security risk because its dependencies and Gentelella/Bootstrap 3 frontend have been abandoned since 2020. You should run software composition analysis and CVE scans, pin dependencies, isolate the app, and harden authentication, RBAC, CSRF, and sessions. For production, plan an upgrade or replacement path before launch, not after.
- What admin theme does the boilerplate use?
- It uses the Gentelella admin theme built on Bootstrap 3. The theme is traditional and browser-compatible, but it has dated accessibility and responsive-design gaps. Most teams should plan to replace it with a maintained theme or admin framework.
- Is this boilerplate suitable for API-only, SPA, or microservice applications?
- No, it is a poor fit for API-first services, SPAs, Inertia/React/Vue frontends, or microservice estates. It is designed as a server-rendered Blade and Bootstrap monolith for traditional admin and back-office apps. Choose a modern API starter or headless admin tool instead.
- What are better maintained alternatives to labs64/laravel-boilerplate?
- Consider Laravel Breeze or Jetstream for authentication scaffolding, or Filament for a modern admin panel, depending on whether you want Blade, Livewire, or Inertia. Current admin starter kits receive security patches and support modern Laravel and PHP versions. Compare upgrade cost, UI roadmap, SSO/MFA needs, and long-term maintenance ownership before choosing.