- Is netbull/auth-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The Composer type is symfony-bundle, and the code uses Symfony bundle and dependency-injection conventions. It integrates with Doctrine ORM and the Symfony Security component, so it belongs in a Symfony application rather than a Laravel one.
- Can I use netbull/auth-bundle in a Laravel application?
- Not as a drop-in dependency. Laravel does not use Symfony's bundle registration or the same security firewall wiring, so adopting it would require a bespoke bridge or reimplementing its service wiring. That effort defeats the purpose of pulling in a package. Choose a Laravel-native authentication package instead.
- What features does netbull/auth-bundle provide out of the box?
- It provides user registration with validation and optional email confirmation, login and logout with remember-me support, password reset with secure expiring tokens, and role-based access control wired into the security firewall. Routes, templates, and the user entity are configurable so you can adapt the flows. It is aimed at reducing boilerplate for common authentication screens.
- What license does netbull/auth-bundle use, and can I use it in a commercial SaaS?
- The package is AGPL-3.0, a network-copyleft license. If you modify it and expose the service over a network, you may be required to disclose the modified source. For a commercial SaaS, that needs legal sign-off and is often rejected outright. Internal tools or AGPL/OSS products are a better fit.
- Which Symfony and PHP versions does netbull/auth-bundle support?
- The provided context does not list supported Symfony or PHP version ranges, so you must verify them in the repository's composer.json before planning a spike. The technical review explicitly flags this question as unresolved. Do not assume current Symfony LTS support without checking.
- Does netbull/auth-bundle use Symfony Security for password hashing and sessions, or roll its own?
- The overview says it integrates with Symfony's Security component, and password reset uses expiring tokens, but the context does not confirm whether hashing, token generation, and session handling are delegated or reimplemented. Because authentication is a high-blast-radius domain, review the code to confirm it uses Symfony's battle-tested primitives. No external security audit is mentioned.
- How do I install and configure netbull/auth-bundle?
- Install it with Composer, enable the bundle in your Symfony kernel or bundles configuration, then configure the security firewall, user entity, and routes. The package exposes configurable routes, templates, and user entity settings so you can tailor the flows. Read the repository README for exact service and configuration keys before wiring it in.
- Is netbull/auth-bundle actively maintained and production-ready?
- Treat it as high risk for production. The technical assessment reports a single maintainer, zero stars, zero dependents, and no downstream projects that would surface bugs before you do. It also notes no external security review of the auth flows. That combination is not field-validated for a high-blast-radius domain like authentication.
- What changed in netbull/auth-bundle v7.0.5, and is v8.0.0 coming?
- v7.0.5 is a single commit titled "added deprecation" with one commit diff from v7.0.4, tagged on 2026-05-29. Shipping a deprecation in a patch release is a semver smell and suggests a future v8.0.0 with removals is plausible. The context does not say what was deprecated, so read commit 7c5c7a8 before any spike. It is not a security release.
- What are alternatives to netbull/auth-bundle for Symfony authentication?
- For Symfony, evaluate alternatives that build directly on symfony/security-bundle and have active maintenance, dependents, and security review. The technical assessment says the opportunity score suggests a gap, but a gap is not a validated solution. If your target is Laravel, use a Laravel-native package instead of bridging this Symfony bundle.