- Can I install highlyprofessionalscum/user-bundle in a Laravel application?
- No. It is a Symfony bundle built for Symfony's DependencyInjection, SecurityBundle, and Doctrine, with no Laravel service provider or facade. Composer may also create conflicting Symfony/Doctrine dependencies in a Laravel app. Use Laravel Breeze, Fortify, Jetstream, or laravel/ui instead.
- Does this package integrate with Laravel's Auth guard or Eloquent?
- No. It targets Symfony's security stack and Doctrine ORM/ODM, not Illuminate Auth, Eloquent models, or Laravel's Guard system. There is no adapter or mapping for Eloquent user providers. For Laravel, use a native auth starter kit or a maintained Laravel auth package.
- What Symfony and PHP versions does this bundle support?
- The provided context does not confirm exact version constraints; Symfony 5.4, 6.x, and 7.x compatibility is unverified. PHP 8.x is assumed but not confirmed. You must inspect composer.json and pin an exact commit because no tagged release is visible.
- Is this a fork of FOSUserBundle, and how is it different from upstream?
- Yes, it is described as a fork of the deprecated FOSUserBundle. The delta versus FriendsOfSymfony/FOSUserBundle is not documented, and it is unclear whether it is a mirror, rename, or functional rewrite. Ask for a diff before considering adoption.
- Is highlyprofessionalscum/user-bundle maintained and safe for production?
- The TPM assessment rates maintenance and security risk as high. It has no visible CI, release tags, maintainer identity, or dependents, and the namespace signals a non-serious project. Authentication code is high-risk, so an unvetted fork is not a defensible production choice.
- What Laravel packages should I use instead for user management?
- Use Laravel's official starter kits: Breeze, Fortify, Jetstream, or laravel/ui for authentication scaffolding. For roles and permissions, spatie/laravel-permission is a maintained option. None of these are Symfony bundles, and this package is not a Laravel alternative.
- How do I install this bundle in a Symfony project?
- You would install it with Composer and register it in Symfony's bundles configuration, then configure security and Doctrine. However, no release tags or documentation are visible, so verify composer.json constraints and pin an exact commit hash rather than a floating dev-master. A time-boxed staging spike on your target Symfony version is essential.
- Does this bundle provide registration, password reset, and email confirmation?
- FOSUserBundle-derived bundles typically package user account flows such as registration, password reset, and profile management, but this fork's exact feature set and security patches are undocumented. You must review the source for password hashing, reset-token, and email-confirmation behavior. Do not assume inherited flows are safe or current.
- Can I use this bundle with Doctrine ODM or a custom user storage?
- The overview states compatibility with Doctrine ORM and ODM plus custom storages. In practice, you will need to verify the mapping, user provider, and storage configuration in the source because documentation is limited. In Laravel there is no viable Doctrine/Eloquent bridge for this bundle.
- What should I check before adopting this fork in a Symfony app?
- Confirm provenance, license, and the diff against upstream FOSUserBundle. Check composer.json version ranges, the absence of release tags, maintainer identity, and any security contact or CVE process. Benchmark against Symfony native Security plus MakerBundle, and use this fork only if a documented gap justifies the risk.