- What is bashy/laravel-campaignmonitor used for?
- It is a thin Laravel integration layer for Campaign Monitor (Marigold/CreateSend). The package provides a service provider, a facade/alias, a publishable config file for the API key and client ID, and container bindings around the official Campaign Monitor PHP SDK. Its scope appears limited to that binding rather than domain logic.
- Which Laravel and PHP versions does bashy/laravel-campaignmonitor support?
- The repository does not document a clear support matrix, and the assessment suggests it was likely built for the Laravel 5.x through 8.x era and pre-8.x PHP. Exact constraints for laravel/framework, illuminate/support, and the Campaign Monitor SDK must be checked in composer.json. Run a Composer resolution test against your target Laravel and PHP versions before adopting it.
- How do I install bashy/laravel-campaignmonitor?
- Install it with Composer using the bashy/laravel-campaignmonitor package name, then follow the package's service provider registration and config publishing steps. You will need a Campaign Monitor API key and client ID in the published configuration. Because documentation is sparse, verify the provider and alias registration against the source after installation.
- Does it wrap the official Campaign Monitor SDK or make raw HTTP calls?
- The package is designed as a wrapper around the official campaignmonitor/createsend-php SDK rather than a hand-rolled HTTP client. The container bindings are the main integration point, so calling code still works with Campaign Monitor's SDK object model. Confirm the SDK dependency and version constraint in composer.json before relying on this behavior.
- Is bashy/laravel-campaignmonitor safe for production?
- Treat it as high risk for production unless you are prepared to own it. The project shows zero stars, zero dependents, no visible CI, no test suite, no changelog, and no release cadence. The integration surface is small, so a safer path is to use it as a reference implementation, fork it with tests, or bind the official SDK behind your own interface.
- Does bashy/laravel-campaignmonitor support webhooks, rate limiting, retries, or idempotency?
- There is no evidence that the package adds webhook ingestion, event-driven subscriber sync, rate limiting, retries, or idempotency handling. It is a thin binding around the Campaign Monitor SDK, so those concerns would need to be implemented in your application layer. Check the source and SDK behavior if you need reliable delivery or duplicate protection.
- Can I use bashy/laravel-campaignmonitor with Laravel 11 and PHP 8.3?
- Probably not without changes. The assessment flags version drift toward older Laravel and PHP releases, so Laravel 11 on PHP 8.3 may fail Composer resolution or runtime checks. Start with a short Composer resolution test; if it fails, reimplement the small binding layer around the official SDK.
- How does bashy/laravel-campaignmonitor handle API credentials and multi-tenant accounts?
- Credentials are expected in the publishable config file as an API key and client ID. The assessment found no documented support for secret managers, per-tenant credentials, multi-account routing, or key rotation. That makes it a poor fit for multi-tenant products without additional credential-handling work.
- Should I use bashy/laravel-campaignmonitor or build my own integration?
- Because the package is only a thin wrapper, a senior Laravel engineer can reproduce the useful binding, config, and facade in under a day. If you need Laravel 10 or 11 support, multi-tenant credentials, webhooks, or a stable abstraction, build an in-house port around the official campaignmonitor/createsend-php SDK. Using the package as a reference is reasonable, but adopting it as a long-term dependency has marginal value.
- Does bashy/laravel-campaignmonitor have tests, CI, or active maintenance?
- There is no visible test suite, CI pipeline, changelog, or release cadence, and the package has zero stars and zero dependents. Abandonment risk is effectively already realized, meaning your team would become the maintainer from day one. Do a license and source review before adding it to composer.json.