Weave Code
Smssender Laravel Package
carpe-hora/smssender
A Laravel package that offers a simple, driver-based API for sending SMS messages through multiple providers. Configure your gateway, compose messages, and dispatch SMS from your application with minimal setup.
The almost missing SMS sending PHP 5.3 library.
Frequently asked questions about Smssender
- Does carpe-hora/smssender support Laravel 10, 11, or 12?
- Almost certainly not without a fork. The package's last release dates to 2014, which implies illuminate/support constraints around Laravel 4.x and PHP 5.4–5.6 syntax, so Composer will likely refuse to resolve it against Laravel 10, 11, or 12. A legacy Laravel 4/5 app may still be able to install it, but you should inspect composer.json before attempting anything.
- How do I install carpe-hora/smssender with Composer?
- Run composer require carpe-hora/smssender only after reading its composer.json constraints, because a modern Laravel project will likely fail dependency resolution. In a legacy Laravel 4/5 application the package may install as-is; you may also need to register the service provider and facade manually if auto-discovery is not supported. Do not force the install with ignore-platform-reqs in a production app without a rollback plan.
- Does carpe-hora/smssender provide a real Laravel notification channel?
- Treat that claim as unverified. Laravel's notification system did not exist until version 5.3, well after this package's 2014 release, so a native Notifiable channel class is unlikely to be present. Read the source for an actual channel implementation before relying on it; if it is missing, the overview's notification support is aspirational marketing text.
- Which SMS providers does carpe-hora/smssender support?
- The overview advertises pluggable drivers for multiple SMS gateways but does not enumerate them in the provided material. Because the package is roughly a decade old, you must verify each bundled driver against the provider's current API; gateway APIs such as Nexmo-to-Vonage and Twilio versioning have changed substantially. Assume the abstraction may be fine while individual drivers are stale or dead until you inspect the source.
- Is carpe-hora/smssender still maintained and safe for production?
- No. It has had no release in about 11 years, no security patching, and no maintainer to escalate to, with only 54 stars and 0 dependents as production signal. The failure mode is insidious: the manager and facade can look clean while the provider glue has rotted. Do not adopt it for a new or actively maintained Laravel application.
- How do I configure provider credentials and the default sender in carpe-hora/smssender?
- The package ships a publishable config file for provider credentials and the default sender, so configuration is intended to be centralized rather than hard-coded per call. However, its config loading and IoC access patterns predate modern Laravel package auto-discovery, so verify how the config is merged and read in your framework version. In a fork or replacement, prefer constructor-injected Illuminate\Contracts\Config\Repository over legacy App::make or $app['config'] access.
- Can I use carpe-hora/smssender outside Laravel?
- The overview claims a framework-agnostic core, but the package is Laravel-centric with a service provider, facade, and manager resolved from the container. Inspect the source for hard dependencies on Illuminate components and App::make before assuming it will work standalone. If you need a framework-agnostic SMS layer, a small in-house driver contract is usually safer than extracting this package.
- How do I send an SMS using SmsSender::send()?
- The advertised API is SmsSender::send(...) through the package facade, after configuring a default driver and credentials. The provided excerpt does not document the exact signature, so read the manager and driver interface to learn what arguments are required. In a new app, prefer Laravel's Notification::route('sms', ...) with a maintained channel instead of this 2014 facade.
- Does carpe-hora/smssender support queues, retries, rate limiting, or delivery receipts?
- There is no evidence in the provided material that it supports queues, retries, rate limiting, or delivery-receipt webhooks; it appears to be a fire-and-forget sender. Those concerns matter in production, so verify the source and driver implementations before assuming any resilience features. If you need them, implement them in your own channel or driver layer rather than relying on this package.
- What should I use instead of carpe-hora/smssender in a modern Laravel app?
- For Laravel 9–12, use Notification::route('sms', ...) with a maintained laravel-notification-channels package, or write a thin in-house SmsChannel plus SmsDriver contract over Laravel's HTTP client. That gives you the same provider-agnostic abstraction with current framework support, security posture, and Http::fake testing. Forking carpe-hora/smssender is only justified for a legacy app or if its driver set is genuinely broad and worth preserving.
Weaver
How can I help you explore Laravel packages today?