- Is mrdanshur/user-bundle compatible with Laravel?
- No. Despite being listed for Laravel, it is a Symfony bundle packaged as symfony-bundle and a fork of FOSUserBundle. Laravel does not provide the Symfony compiler passes, Symfony Security user providers, Doctrine mappings, or Twig integration points that this package relies on. Installing it will not add Laravel routes, guards, Blade views, or user models.
- What is mrdanshur/user-bundle actually?
- It is a 2021 fork of FriendsOfSymfony/FOSUserBundle, distributed as a Symfony bundle. It bundles Symfony-side user management concepts such as a user provider, canonical fields, registration, login, password reset flows, and Twig templates. It is not a Laravel package and does not follow Laravel conventions like service providers or Eloquent.
- Can I install mrdanshur/user-bundle in Laravel 10 or Laravel 11?
- Composer feasibility is very low. The fork targets Symfony 4.4/5.x and PHP 7.2 to 8.0-era components, while Laravel 10 and 11 resolve Symfony 6/7 components. The dependency solver will likely conflict or resolve to a stale subtree that Laravel never boots. Avoid adding it to a Laravel application.
- Does mrdanshur/user-bundle provide login, registration, and password reset routes in Laravel?
- No. In Symfony it wires into the Security component and Twig, but in Laravel it provides no routes, controllers, middleware, guards, or Blade components. You would see no registration form, login route, or password reset flow from the package. Use Laravel Fortify or Breeze for those features instead.
- What Laravel packages should I use instead of mrdanshur/user-bundle?
- Use Laravel Fortify for headless authentication features, or Breeze and Jetstream for starter kits with views and frontend scaffolding. Profile management is usually a controller plus FormRequest, and roles and permissions are handled by spatie/laravel-permission or native gates and policies. These are first-party or well-maintained options that fit Laravel's architecture.
- How do I implement profile management and role-based access in Laravel without this bundle?
- Build a profile controller with FormRequest validation and an Eloquent User model for editable fields and account preferences. Use Laravel gates, policies, or spatie/laravel-permission for roles and permission checks. Blade components or standard Blade views handle the user-facing forms and panels. This keeps everything in Laravel conventions and under your control.
- Is mrdanshur/user-bundle maintained and safe for production?
- There are strong risk signals: zero stars, zero dependents, a single-maintainer fork, and a last release in July 2021. It has no visible security policy or coordinated disclosure channel, and it lacks upstream fixes for Symfony 6/7 and PHP 8.2/8.3. Authentication is security-critical, so an unvetted fork of a sunset bundle is not a suitable production dependency.
- Can I migrate legacy FOSUserBundle data to Laravel using mrdanshur/user-bundle?
- No, the package cannot bridge the frameworks. The realistic path is to keep the existing database schema, drop the Symfony bundle, and write a thin Laravel user provider or import against those tables using Eloquent or the DB query builder. The fork contributes no migration code for Laravel, so it is not part of that path.
- What Symfony and PHP versions does mrdanshur/user-bundle support?
- It is a 2021 snapshot with constraints around Symfony 4.4/5.x and PHP 7.2 to 8.0-era components. It does not provide Symfony 6/7 compatibility or PHP 8.2/8.3 support. That makes it a poor fit even in modern Symfony projects, where make:user and first-party authenticators are the successor path.
- Are there better alternatives to mrdanshur/user-bundle for Symfony user management?
- Yes. Upstream FOSUserBundle is in sunset status; the Symfony-recommended approach is a maker-bundle-generated user entity plus symfony/security-bundle authenticators. For Laravel, use Fortify, Breeze, Jetstream, and spatie/laravel-permission as appropriate. A maintained first-party path is safer than a 2021 fork.