- Is nmure/encryptor-bundle compatible with Laravel?
- No, not natively. It is a Symfony Bundle that ships a Bundle class, DI extension, and Symfony service definitions, none of which Laravel's container or package discovery can consume. You would have to either install Symfony's DI and config components alongside Laravel or bypass the bundle and use the underlying nmure/encryptor library directly. For a Laravel app, the practical answer is to use a Laravel-native encryption solution instead.
- How do I install nmure/encryptor-bundle in a Laravel application?
- Composer will almost certainly fail. A 2017-era bundle typically pins symfony/* to ^2.7 or ^3.0 and PHP to ^5.6 or ^7.0, which conflicts with modern Laravel installs running Symfony 6/7 components and PHP 8.1+. Forcing it with --ignore-platform-reqs or dependency aliasing on a cryptographic component is a serious red flag. Do not install it in production Laravel code.
- Is nmure/encryptor-bundle still maintained?
- No visible maintenance. It has roughly 2 stars, 0 dependents, and no release since December 2017, and there is no visible security disclosure path. That means no CVE monitoring and no upstream fix if a cipher usage issue is found. Treat it as unmaintained and unaudited.
- Is nmure/encryptor-bundle safe to use for production encryption?
- The technical risk is high and concentrated in cryptography, which is the worst place for it. With zero third-party review and no patches since 2017, issues such as padding, IV handling, MAC-then-encrypt ordering, or key derivation would likely go unfixed. Code of that vintage may also silently return false from openssl_decrypt instead of throwing, which in Laravel surfaces as corrupted user data rather than a clean exception. Use a maintained, audited library instead.
- What encryption algorithms does nmure/encryptor use?
- The documentation provided does not specify the primitives. You would need to inspect the underlying nmure/encryptor source to determine whether it uses AES-CBC or GCM, RSA, or libsodium, and whether it provides authenticated encryption. Also check where keys live, whether there is a rotation story, and what KDF and iteration count are used if keys derive from a passphrase.
- Does nmure/encryptor-bundle support Laravel 10 or Laravel 11?
- Assume it does not until proven otherwise. Its Composer constraints target Symfony 2.7/3.0 and PHP 5.6/7.0, while Laravel 10 and 11 require PHP 8.1+ and modern Symfony components. Making it load would require patching composer.json and likely dependency aliasing, which is not appropriate for a crypto dependency. There is no official Laravel 10 or 11 support.
- What should I use instead of nmure/encryptor-bundle in Laravel?
- Start with Laravel's first-party Crypt facade, which provides AES-256-GCM or CBC with HMAC and key rotation via APP_PREVIOUS_KEYS. For asymmetric, envelope, or field-level encryption, use mature ecosystem packages such as defuse/php-encryption, paragonie/halite, or paragonie/sodium_compat. Any of these is a better fit than a two-star Symfony bundle last released in 2017.
- How does nmure/encryptor-bundle compare to Laravel's Crypt facade?
- Laravel's Crypt facade is framework-managed, authenticated, and supports key rotation out of the box. nmure/encryptor-bundle is a thin Symfony configuration layer whose only value is pre-wired service definitions for a framework you are not using. Before adopting it, ask what requirement it satisfies that Laravel's Crypt does not; if the answer is none, the evaluation ends there.
- Can I use nmure/encryptor-bundle with Doctrine in Laravel?
- Only by bypassing the bundle. The bundle's Doctrine integration is wired through Symfony's DI container, which Laravel does not use. If a specific capability in the underlying library is genuinely required, fork the library rather than the bundle, add PHP 8 and Laravel 10-11 compatibility, and wrap it behind a first-party EncryptionService interface bound in a service provider. That keeps framework coupling at zero and preserves the option to swap implementations.
- How do I handle key rotation if I adopt nmure/encryptor?
- There is no documented rotation story in this package. You would have to design key storage, versioning, and re-encryption yourself, and any silent decryption failure would complicate migration. Laravel's Crypt facade already manages rotation through APP_PREVIOUS_KEYS, so for most teams the native solution removes this entire class of risk.