Weave Code
Crypto Bundle Laravel Package
gdbots/crypto-bundle
Symfony bundle that integrates Gdbots crypto services into your PHP application, providing configuration and dependency injection for encryption, signing, and key management. Simplifies wiring secure crypto components and related services.
Symfony bundle that integrates defuse/php-encryption package.
Frequently asked questions about Crypto Bundle
- Can I use gdbots/crypto-bundle in a Laravel application?
- No, not as a direct dependency. gdbots/crypto-bundle is a Symfony bundle built around Symfony's bundle, kernel, and dependency-injection extension model, which Laravel does not run. Laravel can use the underlying defuse/php-encryption library, but the bundle itself provides no usable integration path in a Laravel app.
- Does gdbots/crypto-bundle support Laravel 10, 11, or 12?
- No. Version 5.0.0 requires PHP 8.5+ and Symfony 8.x components, while Laravel 10, 11, and 12 target PHP 8.2–8.4 and ship with Symfony 7.x components. Composer will likely block installation because those constraints collide with Laravel's own Symfony pins.
- What PHP and Symfony versions does gdbots/crypto-bundle v5.0.0 require?
- Version 5.0.0 requires PHP 8.5 or newer and Symfony 8.x components (symfony/* ^8.0). That major-version change narrows the package to bleeding-edge Symfony 8 applications. Current Laravel releases on PHP 8.2–8.4 and Symfony 7.x do not match those constraints.
- How do I install gdbots/crypto-bundle with Composer in Laravel?
- You generally should not attempt it. Running composer require gdbots/crypto-bundle in a typical Laravel 10, 11, or 12 app will either fail dependency resolution or force unsupported PHP and Symfony versions. The practical Laravel path is to install defuse/php-encryption or use Laravel's built-in Crypt facade instead.
- What is the Laravel alternative to gdbots/crypto-bundle for encryption and signing?
- For encryption, use Laravel's Crypt facade or the framework-agnostic defuse/php-encryption library wrapped in a Laravel service provider. For signing, choose a Laravel-owned adapter around a maintained signing library and bind it behind an application contract. The Symfony bundle is best treated as a reference implementation rather than a Laravel dependency.
- Is gdbots/crypto-bundle a replacement for Laravel's Crypt facade?
- No. Laravel's Crypt facade is a first-party Laravel service with framework integration, configuration, and key handling, while gdbots/crypto-bundle is a Symfony bundle for wiring GDBots crypto services. The reusable part for Laravel is the underlying defuse/php-encryption library, not the bundle's Symfony container integration.
- Does gdbots/crypto-bundle handle key management and key rotation?
- The overview lists key management and credential handling as part of the bundle's service wiring. However, the technical assessment notes that key storage, rotation, and multi-tenant key selection remain application responsibilities. The bundle does not remove the need to design those workflows yourself.
- How do I configure encryption and signing services in Laravel without a Symfony bundle?
- Create a Laravel service provider that binds Encryptor, Decryptor, Signer, and key-provider interfaces into the container. Implement them with defuse/php-encryption, Laravel Crypt, or another maintained library, and keep configuration in config files or environment variables. This gives you the DI wiring the Symfony bundle provides without depending on Symfony's bundle extension model.
- Is gdbots/crypto-bundle maintained and safe for production Laravel apps?
- There is little external validation: the package shows 0 stars and 0 dependents, and v5.0.0 is a major release that raises the PHP and Symfony floors. That suggests it is optimized for the maintainers' GDBots/Symfony estate rather than Laravel consumers. For production Laravel apps, prefer a Laravel-owned adapter over a maintained framework-agnostic crypto library.
- Can I use defuse/php-encryption directly in Laravel instead of gdbots/crypto-bundle?
- Yes. defuse/php-encryption is framework-agnostic and can be installed with Composer and wrapped in a Laravel service provider. That avoids the Symfony bundle dependency and the PHP 8.5/Symfony 8 constraints. You still need to handle key storage, rotation, and payload format decisions in your application.
Weaver
How can I help you explore Laravel packages today?