Weave Code
Google Vision Api Bundle Laravel Package
headoo/google-vision-api-bundle
Symfony bundle that integrates Google Cloud Vision into PHP applications, enabling image analysis for labels, text, faces, and safe-search detection via configurable services and simple dependency injection setup.
Symfony Bundle for Google Vision API
Frequently asked questions about Google Vision Api Bundle
- Is headoo/google-vision-api-bundle compatible with Laravel?
- No. It is a Symfony bundle, and its value comes from the Symfony kernel registering the bundle and its DependencyInjection extension; Laravel has no equivalent mechanism, so the configuration tree and service aliases are never wired up. Strip that away and what remains is a thin wrapper over google/cloud-vision, which you can require directly. The package also predates modern Laravel and PHP versions, so Composer resolution against Laravel 10 or 11 will almost certainly fail.
- How do I install headoo/google-vision-api-bundle?
- You would run composer require headoo/google-vision-api-bundle inside a Symfony application, register the bundle in AppKernel or bundles.php, and add your Google credentials to the config tree. Laravel has no bundle registration step, so installing it there gives you nothing usable. Expect the old constraint set (symfony/symfony ~2.8|~3.x, php >=5.5) to block installation on any modern stack anyway.
- What Google Vision features does this bundle expose?
- Per its documentation it covers label detection, OCR/text detection, face detection, landmark detection and safe search. Other Vision capabilities such as logo detection, crop hints and product search are not mentioned, so assume they are not exposed. Each feature is a separate billing and quota line on Google's side, so enable only the ones you actually call.
- How do I configure Google Cloud credentials for the bundle?
- Credentials are supplied once through the Symfony configuration tree, and the bundle's service wrapper builds the Google client for you. That model dates from 2017, before Application Default Credentials and Workload Identity became the default path, so it most likely expects a service account JSON key file. Google now discourages long-lived JSON keys, so prefer ADC on GCP-hosted workloads.
- Which PHP and Symfony versions does the package support?
- The composer constraints point at symfony/symfony ~2.8|~3.x and php >=5.5, and the last release was March 2017. That predates Vision API v1 GA, google/cloud-vision 1.0, Symfony Flex and PHP 7.2+ type modernisation. It will not resolve against a Laravel 10 or 11 application running PHP 8.1 or newer.
- Does the bundle use REST or gRPC, and do I need a PHP extension?
- The documentation does not say, and that matters for your container image. If it pins REST through a 2016-era google/apiclient, you need nothing extra. If it uses gRPC, you inherit the grpc PHP extension, which has to be compiled or installed in every image that runs the code.
- Is headoo/google-vision-api-bundle still maintained?
- No. The last release was 2017-03-21, roughly nine years ago, with no CI, no release cadence and no maintainer SLA. The repository reads as an agency publishing internal tooling rather than a supported library. It sits at around four stars with zero dependents, so there is no downstream battle-testing or issue corpus to lean on.
- Is it safe to use in production?
- Not recommended. A frozen transitive dependency tree will block your next PHP or Laravel upgrade, and the stale auth handling likely locks you into service account JSON keys. There is no security advisory coverage for the package itself, and the small dependency footprint means nobody else is exercising it in production for you.
- Does headoo/google-vision-api-bundle have a test suite?
- There is no visible CI configuration and no evidence of a test suite, so assume none ships with the repository. If you need confidence in behavior you would have to mock the Google client yourself and assert against the wrapper's response mapping. That is extra work for code you would be replacing anyway.
- What should I use instead for Google Cloud Vision in Laravel?
- Use google/cloud-vision directly and write roughly fifty to eighty lines of Laravel glue: a VisionServiceProvider binding a VisionClient interface to a concrete implementation, a config/vision.php file for project ID, credential source and per-feature toggles, and a facade only if ergonomics justify it. You get modern auth, typed returns and a supported dependency tree. Port the bundle's ideas, not its code.
Weaver
How can I help you explore Laravel packages today?