- Is nmalo/fos-user-bundle a Laravel package?
- No. It is a fork of FOSUserBundle, a Symfony bundle built around Symfony's dependency injection container, security stack, forms, validation, and Doctrine. It does not integrate with Laravel's bundle-less architecture or Eloquent ORM. For Laravel authentication, use first-party packages such as Fortify, Breeze, or Jetstream.
- Can I install nmalo/fos-user-bundle in a Laravel application?
- Composer may resolve the package, but it is not usable in Laravel without a rewrite. The bundle registers through config/bundles.php and expects Symfony HttpKernel, Security, Form, Validator, Twig, and Doctrine ORM. Laravel has no bundle system or compatible DI compiler passes, so code reuse is effectively zero. Do not add it to a Laravel project.
- Does nmalo/fos-user-bundle support Laravel 10, 11, or 12?
- No. The package targets Symfony and does not declare Laravel framework support. Its dependencies are Symfony components plus Doctrine, not illuminate/support or laravel/framework. There is no Laravel service provider, facade, or configuration bridge.
- What PHP and Symfony versions does nmalo/fos-user-bundle require?
- The repository does not publish a clear changelog or support matrix in the provided context. Upstream FOSUserBundle is archived and does not support Symfony 6 or 7 or current PHP 8.x, and this fork gives no signal that it has widened that range. Check composer.json and run a dependency resolution audit before considering it even for a Symfony codebase.
- Is nmalo/fos-user-bundle safe to use in production?
- Technical risk is high. It is a zero-star, single-maintainer fork of authentication code with no visible tests, CI, release history, or published diff against upstream. Authentication code touches password hashing, reset tokens, remember-me cookies, and session defenses, where defects are incident-grade. A fork of an abandoned bundle with an unauditable modified delta is not a production-safe choice.
- What is the difference between FOSUserBundle and nmalo/fos-user-bundle?
- nmalo/fos-user-bundle is described as a modified Symfony FOSUserBundle. The provided context offers no changelog, diff, or feature list, so the exact modifications are unknown. Upstream FOSUserBundle is deprecated and archived in favor of Symfony's native user provider and MakerBundle. Treat the fork as an unauditable delta until a full diff is published.
- What should Laravel developers use instead of nmalo/fos-user-bundle?
- Use Laravel's first-party authentication packages: laravel/fortify for headless backends, Laravel Breeze for a minimal scaffold, or Laravel Jetstream for a fuller stack. These are maintained, tested, Laravel-native, and cover registration, login, password reset, email verification, and two-factor authentication. They avoid importing a parallel Symfony security stack.
- Does nmalo/fos-user-bundle work with Doctrine ORM, ODM, and Propel?
- Yes, in a Symfony context the bundle supports Doctrine ORM, Doctrine ODM, and Propel persistence through its user model and mapped superclass. That compatibility is irrelevant for Laravel, which uses Eloquent by default. A Laravel application would need a full persistence rewrite to use it.
- Is nmalo/fos-user-bundle actively maintained?
- There is no evidence of active maintenance in the provided context: zero stars, zero dependents, no CI badge, no release history, and no changelog. Upstream FOSUserBundle is archived and deprecated, so the fork inherits an end-of-life path. Before relying on it, confirm maintainer response commitments, security reporting, and test coverage.
- Can I use nmalo/fos-user-bundle for user registration and profile management in Laravel?
- Not directly. The bundle provides user entities, registration, authentication, and profile workflows for Symfony-style applications, not Laravel. Laravel already ships equivalent functionality through Fortify, Breeze, and Jetstream. Building on those packages is faster and safer than porting a deprecated Symfony bundle.