- Is jord-jd/symfony-password-exposed-bundle compatible with Laravel?
- It is a Symfony bundle, not a Laravel-native package, so Laravel compatibility is not explicitly documented in the release context. It may fit Laravel apps that already use Symfony components or can consume the package as a library. Laravel-only teams should verify service-provider, config, validator, and translation integration before treating it as Laravel-ready.
- How do I install jord-jd/symfony-password-exposed-bundle in a Laravel app?
- Install it with Composer as jord-jd/symfony-password-exposed-bundle, but do not assume Laravel auto-discovery or a Laravel service provider exists. In Symfony it is registered as a bundle with YAML configuration; in Laravel you would need to confirm whether the validator constraints can be wired manually. Test in a staging branch before adding it to production requirements.
- What PHP and Symfony versions does this package support?
- The release context indicates PHP 7.4 through modern PHP and Symfony 4.4 through Symfony 8 support. PHP 7.4 and Symfony 4.4 are legacy lines, so teams should confirm their exact version pairing rather than relying on broad compatibility claims. Laravel version support must be validated separately from Symfony support.
- How does the bundle check if a password has been exposed in a data breach?
- The package is described as a Symfony bundle that checks user passwords against known data breaches so exposed credentials can be blocked at registration and password changes. It integrates with Symfony's validator and password constraints for low-friction setup. The review context does not detail the breach-data lookup mechanism, so verify the implementation and privacy behavior before production use.
- How do I configure the bundle in a Laravel project?
- The package uses Symfony bundle build hooks, compiler passes, and YAML configuration, not a documented Laravel config file. Laravel teams should inspect the YAML defaults and container build behavior, especially because corrected defaults in v1.1.0 may change behavior for teams relying on older documentation. Clear config and container caches after changes and validate translation resolution.
- Can I use this package with Laravel validation for registration and password changes?
- The package integrates with Symfony's validator and password constraints, but the context does not confirm a Laravel validation rule or service provider. You may be able to call the underlying constraints manually if the package can be consumed as a library. Otherwise, a Laravel-native rule or a small adapter may be needed.
- What are the production risks of using this Symfony bundle in Laravel?
- Technical risk is medium-low, with no explicit breaking changes called out, but compiler-pass registration and bundle build-hook ordering can affect container builds in edge cases. Removing the lockfile is correct for a library but can change transitive dependency resolution during upgrades. PHP 7.4 support carries EOL security and support risk, so confirm your runtime is still maintained.
- How should I test this package in Laravel CI?
- Add a CI matrix for lowest and current dependency sets so Composer resolution changes from lockfile removal are visible. Run registration and password-change validation tests, clear config and container caches, and verify translation-contract resolution. Also test on the exact Laravel, PHP, and Symfony component versions used in production.
- What alternatives are available for checking exposed passwords in Laravel?
- Laravel teams often look for Laravel-native validation rules or direct integrations with breach-checking services rather than Symfony bundles. This package is a reasonable option only if your app already uses Symfony components or you can consume it as a library. Compare maintenance, PHP/Symfony support windows, privacy posture, and Laravel-specific integration effort before choosing.
- Is jord-jd/symfony-password-exposed-bundle actively maintained and what support window should I expect?
- The v1.1.0 context shows compatibility and hardening work, including Symfony 8 support, lowest/current regression tests, and lockfile removal. However, retained PHP 7.4 and Symfony 4.4 support mean legacy support burden, and no Laravel compatibility matrix is evidenced. Request a supported-version and upgrade policy before broad adoption.