- Is nucleos/user-bundle a Laravel package?
- No. NucleosUserBundle is a Symfony bundle, the maintained successor to FOSUserBundle, and it depends on Symfony's service container, EventDispatcher, and Security component. It ships Doctrine ORM and ODM mappings and has no Laravel service provider or facade. Laravel applications cannot load it through Composer autoloading alone.
- Can I use NucleosUserBundle in a Laravel application?
- Not without building a custom bridge between Symfony's security stack and Laravel's guards, which is more work than implementing the same user lifecycle natively. Laravel has no bundle system, no Symfony firewalls, and uses Eloquent by default. The practical answer is no integration, so treat the bundle as a design reference only.
- What features does NucleosUserBundle include?
- It provides a user model, registration, login and logout wiring, password reset, profile editing, email confirmation, and optional group and role support. It is intentionally a domain layer with no admin UI, no REST API, no social login, and no token or SPA story. Anything product-facing such as two-factor auth, rate limiting, or audit logging is left to you.
- How do I install nucleos/user-bundle?
- Install it with Composer using composer require nucleos/user-bundle, then register the bundle in your Symfony bundles configuration. You also need to configure a Doctrine mapping, create a User entity extending the bundle's base user class, and wire a security firewall and user provider. Check the repository README for the exact service and configuration keys for your release.
- Which Symfony and PHP versions does NucleosUserBundle support?
- The intended envelope is Symfony 6 or 7 with PHP 8.2 or newer and Doctrine ORM 2 or 3, but verify the composer.json constraints of the specific tag rather than the README. Release metadata for this package has shown inconsistencies, so confirm tags on Packagist and GitHub before committing. Pin a version and run your own compatibility tests.
- Is NucleosUserBundle a good replacement for FOSUserBundle?
- Yes, for existing Symfony applications still running the deprecated FOSUserBundle, this bundle is the realistic migration target. It preserves the familiar user lifecycle while modernising the codebase for current Symfony versions. Plan the migration around a schema diff and a password-migration listener rather than a clean install.
- What should Laravel developers use instead of NucleosUserBundle?
- Use Laravel Fortify for the authentication backend, together with Sanctum or Passport for API tokens and the framework's password broker, notifications, and signed URLs for reset flows. Breeze or Jetstream can supply a starter UI if you need one. These are first-party solutions supported by the Laravel release cycle.
- Does NucleosUserBundle support roles and groups?
- Yes. It offers optional group and role support integrated with Symfony Security, so authorization can be expressed through Symfony's role hierarchy. The bundle provides the domain layer only, so you still build any admin screens for assigning roles or managing groups.
- Is NucleosUserBundle safe to use in production?
- It is MIT licensed with a small maintainer group and no commercial backing, so there is no SLA or guaranteed security-response commitment. Adoption is low, with roughly 61 GitHub stars and no dependents, which means limited battle-testing outside the maintainers' own applications. Audit the code, pin a version, and decide in advance whether you are willing to fork and patch it yourself.
- Can I copy NucleosUserBundle's architecture for a custom Laravel auth module?
- Yes, and that is the most useful outcome for a Laravel team. Its separation of the user model, password updater, event hooks, and mailer abstraction is a clean template for a bespoke identity module, and its password-migration listeners are a pattern worth reusing. Reimplement those ideas with Laravel primitives such as guards, events, notifications, and Fortify actions.