- Is manojx/encrypter-bundle compatible with Laravel?
- No confirmed Laravel compatibility exists. The technical assessment says the package description explicitly targets Symfony bundles, while Laravel uses service providers and its own container. There is no confirmed Laravel adapter or service provider, so adoption would require porting or wrapping it yourself.
- How do I install manojx/encrypter-bundle with Composer?
- The expected command would be composer require manojx/encrypter-bundle, but Packagist presence and autoload validity are unconfirmed in the assessment. Verify the package resolves from Packagist and autoloads correctly before relying on it. For a confidentiality-path dependency, also confirm the license and source repository before installation.
- Does manojx/encrypter-bundle use authenticated encryption?
- The description names AES-256-CBC and does not mention a MAC or AEAD mode. Unauthenticated CBC is malleable and can expose padding-oracle behavior if decryption errors are observable. Verify whether the package performs encrypt-then-MAC or uses an authenticated mode before trusting it.
- What Laravel version does manojx/encrypter-bundle support?
- No Laravel version support is stated. The assessment identifies it as a Symfony bundle with unknown PHP and Symfony version constraints. There is no documented Laravel compatibility matrix, so assume none until verified.
- Can I use manojx/encrypter-bundle to encrypt sensitive data in production?
- The assessment rates this as high risk for production confidentiality use. It cites a single release, zero dependents, no security disclosure policy, no audit, and an unverified NOASSERTION license. For Laravel applications, native Crypt::encryptString and decryptString already provide audited framework encryption. Do not put this package in the confidentiality path without a fork, audit, and license review.
- How does manojx/encrypter-bundle handle encryption keys and rotation?
- The assessment found no stated story for key generation, storage, rotation, or envelope encryption. It also notes no confirmed multi-key or previous-key fallback support for rotation windows. You would need to design and implement key management yourself.
- Is manojx/encrypter-bundle licensed for commercial use?
- The license is listed as NOASSERTION, meaning redistribution and derivative-work rights cannot be confirmed from the repository. For a component in the encryption path, unverifiable licensing is a compliance stop. Resolve an explicit MIT or Apache-2.0 license before commercial adoption.
- Does manojx/encrypter-bundle detect tampered ciphertext?
- The overview claims graceful failure on invalid or tampered payloads, but the assessment warns that CBC without a MAC or AEAD does not provide reliable cryptographic tamper detection. Error handling alone is not a substitute for authenticated encryption. Test malformed-ciphertext behavior and confirm the cryptographic construction before trusting tamper claims.
- What is the Laravel alternative to manojx/encrypter-bundle?
- Laravel's native Illuminate\Encryption\Encrypter and Crypt facade provide AES-256-CBC with encrypt-then-MAC and key rotation via previous_keys. Use Crypt::encryptString and Crypt::decryptString with APP_KEY managed by your secrets store. That is the shortest, framework-supported path for Laravel applications.
- Is manojx/encrypter-bundle actively maintained and tested?
- The assessment reports a single release dated 2024-10-05, zero stars, zero dependents, and a bus factor of one. It found no security disclosure policy, no audit, and no confirmed test suite covering tamper detection or malformed ciphertext. Treat maintenance and test coverage as unverified until the repository proves otherwise.