- Is helppc/encryption-bundle a Laravel package?
- No. Despite being listed in some places as Laravel/PHP, it is a Symfony bundle built around Symfony's DI extension, configuration tree, and container compilation phase. Laravel's container has no compile step, so the package's most valuable property, a misconfigured encryption group failing the build rather than at runtime, does not exist in a Laravel application. Any plan that says composer require and go is wrong and should be rejected in review.
- How do I install helppc/encryption-bundle in a Laravel application?
- You cannot install it and use it directly, because there is no Laravel service provider. The practical path is to adopt the underlying spaze/encryption library, port the named encryption-group configuration schema into config/encryption.php, and write a Laravel service provider that builds configured group instances. Add a boot-time validator so misconfiguration fails fast and loudly, since Laravel has no compile phase to catch it.
- What PHP and Symfony versions does helppc/encryption-bundle support?
- Version 2.1.0 requires PHP 8.4 or higher and Symfony ^7.4 || ^8.0. The 2.1.0 release only widened Symfony major-version support; src/ is byte-identical to 2.0.0. If your estate runs PHP 8.2 or 8.3, adopting this code forces a runtime upgrade across the fleet or a fork that relaxes the constraint.
- How does the encryption group configuration work in helppc/encryption-bundle?
- Configuration is defined through a Symfony configuration tree with named encryption groups, validated during container compilation. The DI extension reads kernel.environment and kernel.build_dir, which are Symfony kernel parameters with no Laravel analogue. In Laravel you would have to fabricate equivalent values or bypass the extension entirely, which removes the compile-time guarantee that makes the bundle worth using.
- Can helppc/encryption-bundle bundle multiple values into a single encrypted string?
- Yes. The bundle is a thin typed facade over spaze/encryption, exposing encrypt and decrypt plus a bundle operation that packs structured values into one portable encrypted string. That core capability carries no framework coupling, which is exactly why a Laravel adapter is feasible even though the bundle itself is Symfony-only.
- What are the alternatives to helppc/encryption-bundle for Laravel encryption?
- Laravel's built-in Crypt facade and Encrypter cover most column and payload encryption needs with no extra dependencies. If you specifically want the bundling semantics, adopt spaze/encryption directly and wrap it in your own service provider. A custom Eloquent cast built on the framework's encrypter is often the smallest correct solution.
- What work is required to integrate helppc/encryption-bundle with Laravel?
- You need a service provider that translates config/encryption.php into configured group instances, a boot-time validator that fails loudly on bad groups, and optionally an Eloquent cast or attribute for column-level use. A key rotation command modelled on GenerateEncryptionKeyCommand, using random_bytes or sodium_crypto_box_keypair, rounds it out. None of this is research; it is genuine implementation and ongoing ownership.
- Does helppc/encryption-bundle have tests and CI?
- Yes. The 2.1.0 release runs PHPUnit, PHPStan level 10, PHPCS, Rector, and composer validate --strict green across three pinned stacks. Flex is used to prevent transitive float between Symfony majors. That is better hygiene than a one-star package usually implies, but hygiene is not adoption and it does not change the ownership calculus.
- How do I rotate encryption keys with helppc/encryption-bundle?
- There is no rotation command in the bundle, so model one on GenerateEncryptionKeyCommand using random_bytes or sodium_crypto_box_keypair. Keep new keys alongside old ones and decrypt with the old key before re-encrypting with the new one. Because this is source you own, plan rotation as part of your adapter rather than waiting for it upstream.
- Is helppc/encryption-bundle actively maintained and safe to depend on?
- It is MIT licensed with one star, zero dependents, and a single maintainer. Version 2.1.0 improves the maintenance signal by widening Symfony support and enforcing CI, but it does not change the bus factor. Treat it as source code you intend to own and review, and note that the same organisation publishes a near-identical fork that this bundle is explicitly forbidden from depending on.