- Is focusly-app/mailchimp-bundle a Symfony bundle or a Laravel package?
- The record is contradictory: the Composer package name and package metadata describe a Symfony bundle, while the provided description claims a Laravel service provider with facade and DI support. Both cannot be true for the same coherent artifact, so treat the documentation as unvalidated marketing copy until you read composer.json and src/. That single verification gates every other adoption decision.
- Can I use focusly-app/mailchimp-bundle in a Laravel application?
- Not idiomatically. Laravel does not provide usable HttpKernel bundle wiring, config/bundles.php, or Symfony container extension compilation, so a Symfony bundle cannot be consumed the way a Laravel package would be. The workable Laravel paths are forking and re-wiring the package or copying the client class into your own service provider, which is effectively a rewrite you own.
- What Mailchimp API endpoints does this package cover?
- The package is described as plumbing for a narrow slice of Mailchimp Marketing API v3: subscribing, updating, and unsubscribing members, plus reading lists, members, and campaigns. It wraps credentials in configuration and exposes services through the container. There is no capability listed that you cannot get from Mailchimp's official mailchimp/marketing SDK or direct REST calls.
- How do I configure the Mailchimp API key and server prefix?
- Configuration is described as bundle-level settings for the Mailchimp API key and server prefix, with the client wired into Symfony's dependency injection container. The record does not include actual config keys, YAML examples, or environment variable handling. Inspect the bundle's Configuration and Extension classes before assuming how credentials are injected.
- Does this package support Symfony dependency injection and autowiring?
- The description claims Symfony DI integration with autowiring support, which is the package's only differentiated value. That value is conditional on the bundle matching your framework and Symfony version era. Because the published metadata lacks Symfony constraints, autowiring support should be verified against your pinned symfony/* versions rather than assumed.
- Which Symfony versions does this Mailchimp bundle support?
- The available metadata does not state a Symfony version constraint, PHP constraint, or last commit date. The TPM assessment suggests a likely Symfony 3.x/4.x vintage, which could conflict with modern symfony/* pins. Check composer.json and the repository history for constraints, CI status, and test coverage before installing.
- Is focusly-app/mailchimp-bundle production ready and actively maintained?
- Treat production adoption as high risk. The package has zero stars, zero dependents, and no evidence of production use, and the record is missing license, PHP and Symfony constraints, test suite, CI status, and dependency details. It also has a single maintainer and no disclosed security policy, so there is no clear path for fixes or vulnerability reports.
- Does this package handle PII, GDPR, or compliance requirements?
- The package handles email addresses, merge fields, and audience segmentation, which are PII-adjacent data and may trigger GDPR, CCPA, vendor-risk, and supply-chain review. The record shows no security disclosure policy and no provenance beyond a single maintainer. If third-party packages touching customer PII require a compliance gate, assume this package fails it until proven otherwise.
- What are alternatives to focusly-app/mailchimp-bundle for Mailchimp in Laravel?
- For Laravel, use Mailchimp's official mailchimp/marketing SDK or direct REST calls behind a thin internal adapter you control. For Symfony, a maintained Mailchimp bundle or the official SDK wired through your own service definition is more predictable. This package's only claimed advantage is container ergonomics, and that advantage depends on the framework identity that remains unresolved.
- How should I test or evaluate this package before adopting it?
- First read composer.json and src/ to verify whether the artifact is Symfony, Laravel, or neither; that answer gates everything else. Then check license, PHP and Symfony constraints, last commit date, test suite, CI status, and the transitive HTTP dependency. For contract testing, secure a Mailchimp Marketing API key and sandbox audience with marketing ops, which is a real lead-time item.