- Is misteio/cloudinary-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The name and package type indicate bundle registration through a Symfony Extension and CompilerPass, which Laravel has no equivalent mechanism for. In Laravel you would be adopting a Symfony-shaped adapter and writing your own service provider glue. For a Laravel codebase the architecture fit is poor to moderate.
- How do I install misteio/cloudinary-bundle in a Laravel application?
- You can composer require it, but there is no supported Laravel integration path. You would need to hand-write a service provider that binds the bundle's configuration array and resolves the Cloudinary API client from the container. Expect composer why-not conflicts against current illuminate/* versions and PHP 8.x because of vintage constraints. For greenfield Laravel work, use the official Cloudinary integration or a purpose-built provider instead.
- What does misteio/cloudinary-bundle actually add beyond the official cloudinary_php SDK?
- Based on the assessment, the wrapper mainly adds configuration binding and a dependency-injection alias around the official cloudinary/cloudinary_php SDK. It is a small amount of code to own or reimplement. It is unclear whether it exposes signed URL helpers, upload presets, or transformation builders beyond that. If it is only DI wiring, the build-versus-adopt case collapses.
- Which cloudinary_php SDK version does misteio/cloudinary-bundle require, and is it still maintained?
- The package is vintage and likely pins an older major of cloudinary/cloudinary_php. The exact constraint must be checked in its composer.json. That pinned SDK major is the real security surface for credential handling, signed uploads, and URL signing, so confirm it still receives patches. An unmaintained wrapper pins you to an unmaintained SDK version.
- Does misteio/cloudinary-bundle support PHP 8 and Laravel 10 or 11?
- Do not assume support. A bundle of this vintage is likely constrained to older PHP and older Cloudinary SDK majors. Run composer why-not against your target PHP and Laravel versions before committing. Expect conflicts with current illuminate/* releases and PHP 8.x.
- What is the best alternative to misteio/cloudinary-bundle for Laravel?
- Use the official Cloudinary Laravel integration if one fits your needs, or build a thin service provider over the official cloudinary/cloudinary_php SDK. That is roughly a day of work and fully under your control. You can copy the bundle's config schema for familiarity while keeping the public surface identical so a later swap is invisible to callers.
- How do I migrate away from misteio/cloudinary-bundle to the official Cloudinary SDK?
- Introduce a CloudinaryClient interface in your domain layer and make the bundle the first adapter behind it. Then swap in the official SDK or a first-party provider as a one-file change. Keep method signatures stable so callers are unaffected. This isolates the eventual migration.
- Does misteio/cloudinary-bundle work with Laravel config caching and environment variables?
- Verify this before relying on it. Laravel's config:cache will break any closure-based config or env-read-at-runtime assumptions the bundle makes. Test config caching explicitly in a staging environment. Also confirm environment separation for dev, staging, and production cloud names and credential rotation.
- Is misteio/cloudinary-bundle safe for production and actively maintained?
- The adoption signal is weak: 8 stars, 0 dependents, and a composite score of 0.16. That is the classic signature of an abandoned or single-author side project, with no visible test or CI signal and no clear release cadence. Supply-chain exposure comes from the pinned, unmaintained SDK version. Treat it as a reference implementation rather than a production dependency.
- Can I use misteio/cloudinary-bundle for signed Cloudinary URLs and upload presets?
- The assessment notes it is unclear whether the wrapper exposes signed URL helpers, upload presets, or transformation builders beyond config binding. Confirm the Cloudinary account-level API you need is reachable through the wrapper. If not, you will end up calling the official SDK directly anyway. In that case, build the thin provider yourself.