- Is royalpunk/mailjet-bundle a Laravel package or a Symfony bundle?
- It is described and named as a Symfony bundle, with Symfony service-container integration, bundle configuration, and autowiring conventions. The available overview does not show a Laravel service provider, publishable Laravel config, or a Laravel mail transport binding. For a Laravel application, treat it as non-native until source review proves otherwise.
- Is royalpunk/mailjet-bundle on Packagist, and how do I install it with Composer?
- The repository is hosted on a self-hosted forge rather than GitHub or GitLab, and the context shows no evidence of a Packagist listing. Composer likely needs an explicit vcs repository entry plus credentials for that forge in every developer environment and CI runner. A plain composer require is unlikely to resolve without that setup.
- Does royalpunk/mailjet-bundle support Laravel 10 or Laravel 11?
- The provided context does not declare Laravel or PHP support ranges at all; it only describes Symfony bundle conventions. It also does not state which illuminate/* constraints, if any, are present. Verify the composer.json constraints and run a hands-on spike before assuming compatibility with any Laravel version.
- What does royalpunk/mailjet-bundle do that Laravel's built-in Mailjet mailer does not?
- The overview only covers credential configuration, a Mailjet client service, and sending transactional emails through Mailjet templates. Laravel already offers a Mailjet mail transport via Symfony Mailer plus the official Mailjet SDK. The bundle would only be worth adopting if source review shows webhooks, template or contact management, batch sends, or multi-tenant routing.
- How do I configure the Mailjet API key and secret in royalpunk/mailjet-bundle?
- The bundle is intended to let you define Mailjet API credentials in Symfony configuration rather than hard-coding keys in application code. The exact configuration keys are not included in the provided overview, so check the bundle's DI extension and README. In Laravel, the comparable path is a mailer DSN with environment variables.
- Can royalpunk/mailjet-bundle send Mailjet transactional templates?
- Yes, the overview states it can send transactional emails using Mailjet templates. It does not describe template versioning, contact-list sync, campaign or batch APIs, or webhook ingestion. Those missing capabilities matter if you need more than a simple template send.
- Does royalpunk/mailjet-bundle have a test suite?
- The provided context does not mention a test suite, and there is no downstream evidence such as stars or dependents showing clean installs or working usage. It is also not stated whether any tests run against a Mailjet sandbox or only mocks. Treat test coverage and sandbox validation as open questions for source review.
- Is royalpunk/mailjet-bundle maintained and licensed for production use?
- The assessment reports a single maintainer, no visible license, changelog, or contribution history, and no disclosure policy. There are zero stars and zero dependents, so there is little downstream evidence of production use. Treat provenance, licensing, and supply-chain review as blockers rather than formalities.
- Which Mailjet PHP SDK version does royalpunk/mailjet-bundle pin?
- The provided details do not state which Mailjet SDK major is pinned or whether that version still receives security fixes. A stale SDK pin is a likely breakage point at the next framework upgrade. Inspect composer.json and the lock file before using it.
- Should I use royalpunk/mailjet-bundle in a Laravel production app?
- Only if a named gap justifies it, such as webhook processing or template and contact management that you would otherwise build yourself. For ordinary transactional mail, Laravel's built-in Mailjet transport is the lower-risk, upgrade-safe choice. If you adopt it, fork it into an internal namespace, pin a commit SHA, and wrap it behind your own MailTransporter interface.