- Is marrouchi/upload-crop-image-bundle a Laravel package?
- No. marrouchi/upload-crop-image-bundle is a Symfony2 bundle, not a Laravel package. It ships a Bundle class, dependency-injection extension, YAML/XML service definitions, and Twig templates, with no Laravel service provider, facade, or publishable config.
- Can I install this package in a Laravel 10 or 11 application with Composer?
- In practice, no. Laravel has no bundle registry or AppKernel, and the bundle's Symfony2-era dependencies likely conflict with the symfony/* v6/v7 components required by Laravel 10 and 11. Forcing Composer resolution is not a supported installation path.
- What functionality does this bundle provide for image upload and cropping?
- It combines image upload and cropping into a single widget, with configurable constraints and server-side handling so cropped or resized files can be saved. The processing flow is roughly validate upload, open image, apply crop coordinates, resample, and write file. The surrounding integration is Symfony2-specific.
- Does it include a Laravel service provider, facade, or publishable config?
- No. There is no composer.json-declared Laravel service provider, no Facade, no config/ publishable namespace, and no Blade views. The bundle uses Symfony bundle conventions and Twig templates that Laravel does not register or render.
- What are the best Laravel alternatives for server-side image cropping?
- For Laravel 10/11, use maintained packages such as intervention/image for the image-processing primitive and spatie/laravel-medialibrary for conversions and storage orchestration. Pair them with a current client-side cropper for the selection UI. That combination covers the same use case with PHP 8 and Laravel filesystem support.
- Is this package maintained and safe to use for production image uploads?
- Treat it as high risk. The last release was 2015-06-30, Symfony 2.x has been EOL since November 2018, and the package has 11 stars, zero dependents, and a single maintainer. It handles user-supplied binary uploads and filesystem writes with no recent security response, so production use is not advisable.
- Can I port the crop logic from this Symfony bundle into Laravel?
- A port is viable as source material, not as a dependency. The actual crop domain logic is probably only 100 to 200 lines, but it is entangled with Symfony2 idioms such as getRequest(), $this->get('service'), annotation routing, and Twig path helpers. A fork-and-extract is a reasonable one-to-two-day spike if you isolate the crop class and strip the framework coupling.
- Which PHP and Symfony versions does this bundle require?
- The bundle predates PHP 7 scalar type hints and return types and was built for Symfony 2.x, so PHP 8.2 and Laravel 10/11 are outside its support envelope. Exact composer.json PHP and symfony/* constraints should be audited before any reuse. Do not assume modern Laravel version support.
- Does the bundle support GD, Imagick, and EXIF orientation?
- The available evaluation does not confirm whether image handling uses GD, Imagick, or both, or whether EXIF orientation is honored. These are key questions for the maintainer and should be verified in the source before porting. Modern Laravel alternatives document these behaviors more clearly.
- Is there a test suite, license, or active maintainer for this bundle?
- There is no test suite indicated in the available information, the license should be audited in composer.json, and the project has a single maintainer with no dependents. That means little community vetting or real-world hardening. If you fork it, assign ownership and maintenance responsibility explicitly.