- Is performer/rer-user-bundle compatible with Laravel?
- No. performer/rer-user-bundle is a Symfony bundle with a bundle class, DependencyInjection extension, Doctrine mappings, and Symfony Security wiring. It has no Laravel service provider, no extra.laravel metadata, and no publishable config, so Laravel will not boot it. Composer may install the files, but it is a runtime no-op in a Laravel app.
- How do I install performer/rer-user-bundle?
- In a Symfony project you would install it with composer require performer/rer-user-bundle and enable the bundle in your kernel or bundles.php. The README excerpt provided is empty, so confirm the exact registration steps and required Symfony and Doctrine constraints in the repository. In Laravel the command only downloads code; there is nothing to register or boot.
- What Laravel versions does this package support?
- None. The package is built for Symfony, not Laravel, and does not declare Laravel framework constraints or Illuminate dependencies. Do not expect compatibility with Laravel 10, 11, 12, or any other Laravel release. If you need Laravel authentication, use a Laravel-native package instead.
- What does RER mean in performer/rer-user-bundle?
- The repository and package description do not document what RER stands for. It appears to be Performer-specific terminology tied to the vendor's RER-based applications. Treat the undefined acronym as a semantic risk and confirm the meaning with the maintainer before assuming it matches your domain model.
- Does this bundle include user registration, login, and admin screens?
- The package blurb claims ready-made user entities, authentication, registration, role handling, and admin screens. The sparse documentation and empty README excerpt mean you must review the source to confirm which of those concerns are actually implemented. Do not assume it is a complete drop-in authentication scaffold without checking.
- Which Symfony and Doctrine versions are supported?
- The provided materials do not state the exact PHP, Symfony, or Doctrine ORM constraint matrix. Inspect composer.json for require constraints and check whether it targets a supported Symfony release or an end-of-life branch. Also verify Doctrine ORM mapping compatibility before installing it into an existing application.
- Can I use this bundle for role-based access control in Laravel?
- Not directly. The bundle relies on Symfony Security roles and voters, while Laravel uses guards, Gate, and policies with Eloquent models. Making it work would mean either bootstrapping a Symfony kernel inside Laravel or porting the wiring to Laravel, which is a reimplementation rather than an integration. Use Laravel policies or a maintained package such as spatie/laravel-permission instead.
- Is performer/rer-user-bundle safe to use for production authentication?
- Treat it as high risk. It has very low adoption, a single maintainer, sparse documentation, and no described security disclosure or audit process, yet it sits on the authentication and PII path. Production use would create audit evidence and dependency-review burden unless the vendor provides support and you complete a security review.
- What are the best alternatives for user management in Laravel?
- For Laravel, use framework-native options such as Laravel Breeze, Jetstream, or Fortify for authentication, plus Gate and policies or spatie/laravel-permission for roles. For Symfony projects, use Symfony Security with MakerBundle and a maintained user bundle. These options have active maintenance, clear documentation, and community support that this package lacks.
- Is performer/rer-user-bundle actively maintained, tested, and licensed for commercial use?
- The available signals are weak: about 3 stars, zero dependents, an aggregate score around 0.015, and sparse documentation. Test coverage, CI, changelog, last release date, and license terms are not established in the provided material, so verify them before any commercial fork or redistribution. Without a vendor support contract and a clear license, do not adopt it.