- Is schvoy/user-bundle compatible with Laravel?
- The package name follows the Symfony bundle naming convention, and its documented foundation is a Doctrine-backed user entity, so Laravel compatibility is not established by default. Before adopting it, confirm the repository ships a Laravel service provider, a publishable config namespace, and does not depend on Symfony HttpKernel or EventDispatcher primitives that Laravel only partially mirrors. The available evaluation notes explicitly flag this as unverified and require re-validation against the actual code. Treat it as a greenfield evaluation rather than a drop-in Laravel package.
- How do I install schvoy/user-bundle with Composer?
- Composer installation itself is assumed to be mechanical, but the safer approach for evaluation is to pin the exact version rather than a caret range. Require schvoy/user-bundle:1.2.0 for the entire evaluation window and record the resolved commit SHA alongside the tag. Verify that the tag resolves to a verifiable commit before anything reaches a shared branch. No composer metadata or install instructions were included in the supplied materials, so check the repository's composer.json first.
- Does Schvoy User Bundle replace Laravel Breeze, Jetstream or Fortify?
- The package overlaps heavily with Laravel's first-party authentication options: Breeze, Jetstream, Fortify and laravel/ui all already own user records, authentication flows and password handling. The real question is not whether it can be installed but whether it replaces, wraps, or conflicts with the auth stack you already run. Stacking two systems that both manage user records and sessions is a common source of hard-to-debug failures. For role and permission work specifically, spatie/laravel-permission is the more Laravel-native alternative to evaluate.
- Which Laravel and PHP versions does schvoy/user-bundle support?
- This cannot be determined from the artifacts supplied, which contained no composer.json, README or release body. Look for declared illuminate/* constraints to see whether they are broad ranges or pinned to specific Laravel majors. Then check the CI matrix to see which PHP and Laravel combinations are actually tested, not just declared. Version support claims that only exist in a composer.json without CI coverage should be treated as unverified.
- Does Schvoy User Bundle ship migrations that modify the users table?
- The package provides a configurable user entity and model with Doctrine-backed persistence, but whether it ships migrations, factories, seeders, routes or views was not confirmed in the supplied materials. Packages that own or alter the users table are high integration cost by default, because the real work is schema and auth-flow reconciliation, not installation. Check specifically whether any migrations overlap or alter Laravel's default users table and whether they are reversible. If they are not reversible, plan a rollback strategy before testing in any shared environment.
- How does Schvoy User Bundle handle authentication, password hashing and session handling?
- The package advertises authentication and security integration hooks rather than a complete standalone auth stack. Confirm whether password hashing delegates to the framework's Hash facade or rolls its own implementation, and the same for session drivers and remember-token handling. Anything touching user records, password hashing or sessions carries outsized failure cost relative to a typical utility package. This is the single most important item to verify in code before adoption.
- Does Schvoy User Bundle support roles and permissions?
- Role and permission support is listed among the package's core features, alongside a configurable user entity and extensible services. The depth of that support is unclear: a simple role column is very different from a full permission and policy layer. Review how roles are stored, whether permissions are granular, and how the checks integrate with Laravel gates and policies. If you need rich permission modelling, a dedicated Laravel package may be a better fit.
- What changed in schvoy/user-bundle v1.2.0?
- The only artifact supplied for v1.2.0 was a compare link from v1.1.0 to v1.2.0, with no release body, commit list or changelog excerpt. That means breaking changes, deprecations and security fixes cannot be triaged from the release itself, and a minor version bump is not a safety guarantee unless the maintainer is demonstrably semver-disciplined. Read the diff commit by commit and check whether a CHANGELOG.md exists in the repository that the release body simply failed to mirror. The absence of a release summary is itself a signal about release hygiene.
- Is schvoy/user-bundle actively maintained, and what is the bus factor?
- This is a single-namespace personal repository, so contributor count, release cadence and issue-triage latency are the dominant long-term risks for an auth-adjacent dependency. A v1.2.0 on a v1.x line indicates a stabilising but not yet mature API surface with a short track record. Review commit history and open-issue ratio over the last twelve months before committing to it. If you adopt it, plan to vendor or wrap the parts you depend on so an abandoned upstream does not block you.
- How should I test schvoy/user-bundle before using it in production?
- Run the evaluation in a disposable Laravel application rather than a production service, pinned to version 1.2.0 with the commit SHA recorded. Exercise registration, login, role checks, password resets and any remember-token behaviour end to end, then verify migrations run and roll back cleanly. Check for transitive dependencies such as Doctrine DBAL, Symfony polyfills or a specific hash library, since these affect upgrade risk. Only after those checks pass should you consider wrapping it behind your own abstraction layer.