- Can I use javihernandezgil/nexmo-bundle in a Laravel application?
- No. It is a Symfony2 bundle, not a Laravel package, and Laravel cannot resolve its Symfony DependencyInjection extensions, Configuration tree, or service YAML. There is no service provider, publishable config, facade, or Laravel HTTP client binding. Use it only as a reference for wiring patterns, not as a Composer dependency.
- Is javihernandezgil/nexmo-bundle still maintained?
- No. The repository has been archived since its last release in March 2016, with 7 stars and 0 dependents. There is no community maintaining it and no security response path. Any adoption would import an unmaintained dependency chain.
- How do I install it with Composer?
- You can run composer require javihernandezgil/nexmo-bundle, but it is not recommended for Laravel. The package is a Symfony2 bundle archived since 2016, and its dependency chain targets old PHP and Guzzle versions. In a modern Laravel app, installation will likely conflict or leave you with unmaintained code.
- Which Laravel and PHP versions does it support?
- None in any supported sense. It predates modern Laravel and targets Symfony 2.x, an older Nexmo PHP client, and legacy Guzzle and PHP constraints. Laravel 10, 11, and 12 dependency graphs will conflict, so treat it as not compatible.
- How do I configure Nexmo credentials with this bundle?
- It uses a Symfony DependencyInjection Configuration tree and Resources/config service YAML, not Laravel config files. You would define Nexmo credentials in Symfony YAML for the bundle's client factory. In Laravel, the equivalent is config/services.php plus environment variables, which you must author yourself.
- Does it work with Vonage's current SMS API?
- No, it targets the pre-rebrand Nexmo PHP client and 2016 API assumptions. Nexmo is now Vonage, and the SDK lineage, auth model, endpoints, and credential handling have moved on. Behavior against the current Vonage API is unverifiable without live testing, so do not assume it works.
- What are the production and security risks?
- High. The repository is archived with no security response path or CVE monitoring, and it pulls unpinned 2016 transitive dependencies. The failure mode is often a partially working port that breaks on retries, webhook parsing, or unicode and multipart SMS, not a clean install error.
- What is a good Laravel alternative for sending SMS through Vonage?
- Use the current vonage/client SDK behind a Laravel service provider, or a maintained Laravel notification channel for Vonage. Bind a client from config/services.php, inject it through an interface, and send through a queued job with retry and idempotency keys. Expose delivery receipts through a signed webhook controller.
- Can I fork this bundle and reuse its code in Laravel?
- MIT licensing permits forking and internal relicensing, so reuse is legally clean. Technically, the reusable surface is small: a config schema, a client factory, and a message DTO shape. Reproduce those idiomatically in Laravel rather than copying the Symfony container wiring.
- How should I test a Laravel SMS integration if I use this bundle as reference?
- Do not test the bundle as a Laravel dependency. If you use it as a reference, test your own Vonage adapter with a fake HTTP client and contract tests against a Vonage sandbox, and assert queued job retries and idempotency. Keep live SMS tests out of CI except for a small, explicitly gated smoke suite.