- Is leandro980/skebby-bundle a Laravel package or a Symfony bundle?
- The name and repository layout point to a Symfony bundle: there is a bundle class, a DI extension and a services.yaml, not a Laravel service provider. There is no publishable config file, no facade and no bootstrapping written for Laravel's kernel. Check the type field in composer.json before assuming Laravel auto-discovery will register anything. Until that is confirmed, treat it as a Symfony bundle that does not fit a Laravel app out of the box.
- How do I install leandro980/skebby-bundle in a Laravel application?
- Composer install is only the first step: run composer require leandro980/skebby-bundle and watch whether Composer resolves it against your PHP and framework constraints. Because it appears to be a Symfony bundle, Laravel's package discovery will probably not wire the services for you, so you would need to register the classes manually in a service provider. Install it only behind your own interface so it can be removed in a single commit if it does not work. Test against a Skebby sandbox account, never production credentials.
- Does leandro980/skebby-bundle support Laravel 10, 11, 12 and PHP 8.3 or 8.4?
- The last release was on 2021-12-16, which places it in the PHP 7.x and Laravel 8 era, roughly four years of drift from current versions. There is no evidence of updates for Guzzle major versions or PSR-18/PSR-17 interface changes. Run composer why-not leandro980/skebby-bundle against your actual PHP and Laravel matrix and record the resolved versions before any spike. Do not assume compatibility from a successful install alone.
- Which Skebby API generation does the package target, REST or the legacy gateway endpoints?
- That is unclear from the available documentation and is a key risk given the 2021 release date. Skebby's current REST API may differ from older SOAP or gateway surfaces, so a four-year-old client could be calling deprecated endpoints. Confirm the live contract with a direct curl request to Skebby's current send endpoint before trusting the package. Use the package at most as reference documentation for the payload shape.
- How do I send an SMS through Skebby from Laravel without this package?
- Skebby sending is a single authenticated HTTP call: credentials, a recipient list, a message body with a sender alias, and a response containing a message ID. Use Laravel's Http client with credentials read from config/services.php backed by environment variables or a secret manager, never committed. Wrap it in a queued job with exponential backoff, an idempotency key and a dead-letter path. Persist every attempt to an sms_messages table with the provider message ID, segments, cost estimate, status and a correlation ID.
- Does the package handle Skebby delivery reports, webhooks or scheduled sends?
- Nothing in the overview or repository signals support for delivery receipts, webhooks or scheduled delivery. The stated scope is sending messages, checking credits and handling delivery notifications, but the implementation depth is unknown and likely thin. If you need confirmations in your domain logic, plan to receive and verify them yourself. Ask the maintainer directly before relying on any of it.
- How does Skebby bill unicode and concatenated multi-part SMS messages?
- SMS billing depends on encoding: GSM-7 fits 160 characters per segment, while UCS-2 (unicode) drops to about 70, and anything longer is concatenated and billed per segment. A small wrapper from 2021 probably does not compute or expose segment counts, so calculate them client-side before sending. Log the estimated segment count and cost alongside every attempt so billing surprises are traceable. Rate-limit behaviour is another operational detail the package is unlikely to model.
- Is leandro980/skebby-bundle maintained and safe to use in production?
- It shows no releases since 2021-12-16, one star, zero dependents and a single maintainer, with no visible CI, test suite or CVE disclosure path. Giving an unvetted package write access to outbound messaging credentials is real supply-chain exposure. The abstraction is also thin, so the value over a roughly 100-line internal client is marginal. Treat it as a reference for the Skebby payload contract rather than a dependency.
- How should I test Skebby SMS sending in a Laravel app?
- Define an App\Contracts\SmsSender interface with a single send method and bind it in a service provider. Provide a FakeSmsSender for feature tests, or use Http::fake() to assert the outgoing payload shape, headers and recipient list. That way tests never hit the vendor and swapping implementations stays a one-line config change. If you do evaluate the package, keep it behind the same interface so it cannot leak into domain code.
- What are the alternatives to leandro980/skebby-bundle for Skebby SMS in Laravel?
- The strongest alternative is a small in-house client behind an SmsSender contract, using Laravel's Http client and a queued job for retries. You keep full control over payload shape, unicode segmentation, logging and idempotency, which an opaque wrapper takes away. If Skebby is a mandated vendor, you still do not need the package: the integration is one authenticated POST. Other SMS providers can sit behind the same interface if you ever need to switch.