- Is mpp/universign-bundle compatible with Laravel?
- No, not natively. It is a Symfony bundle that registers through Symfony's Kernel and relies on DependencyInjection, EventDispatcher, and likely PSR-18 HTTP wiring, none of which Laravel provides out of the box. In Laravel you should treat it as a reference implementation and budget for an adapter layer rather than expecting composer require to produce a working integration.
- How do I install and configure mpp/universign-bundle?
- Install it with Composer and register the bundle in your Symfony bundles.php or Kernel, then supply Universign API credentials and endpoint settings through your Symfony configuration and environment variables. In a Laravel application there is no bundle registration step, so you would need to instantiate the underlying client or services manually from a service provider and publish equivalent configuration into config/.
- Which Laravel versions does mpp/universign-bundle support?
- None directly. The package is shaped as a Symfony bundle, so Laravel 9, 10, 11, and other versions are not supported through native service-provider auto-discovery. If you must use it in Laravel, you own the compatibility adapter and should verify it against your specific Laravel and PHP versions.
- What does mpp/universign-bundle actually do for Universign signature requests?
- It wires Universign's electronic signature services into Symfony's dependency injection container, providing configurable API credentials, endpoints, service definitions, and support for document signature requests. The likely surface area includes signature-request creation, signer and workflow configuration, document upload, and status retrieval. Webhook verification, idempotency keys, and evidence-package retrieval are not evidenced in the package description, so confirm them before relying on the bundle for a full workflow.
- How can I test Universign integration without sending real signatures?
- Use Universign's sandbox endpoints and switch credentials and base URLs through environment-specific configuration. Keep the bundle's client behind an application-owned interface so you can inject a fake or mock in tests and avoid real API calls. Because the package has zero stars and zero dependents, start with a standalone spike against the Universign sandbox before committing it to a sprint.
- Does mpp/universign-bundle handle Universign webhooks and signature verification?
- The package description does not mention callback handling, webhook signature verification, or replay protection. For any e-signature integration those are the highest-severity correctness risks, so plan to implement authenticity verification and idempotency yourself. Do not assume a thin wrapper enforces webhook trust.
- Is mpp/universign-bundle safe to use in production?
- There is no external evidence base: zero stars, zero dependents, and effectively one maintainer at Mon Petit Placement. The mechanical integration is low risk, but you should audit logging, error reporting, and queue payloads so document bytes and signer PII are not leaked. Treat the first integration as a spike and validate behavior against Universign's sandbox before production commitment.
- What are the alternatives to mpp/universign-bundle for Laravel e-signatures?
- Prefer Universign's REST API directly or a supported Universign SDK, wrapped in a Laravel service provider behind a single application-facing interface. Use this bundle only to learn the request and response shapes if you are in Laravel. That removes the Symfony framework mismatch entirely and gives you control over webhook verification and PII handling.
- How do I keep vendor Universign classes out of my Laravel domain layer?
- Define an application-owned SignatureProvider interface and implement it in an adapter that lives in your infrastructure layer. The adapter may use the bundle's services or the Universign client, but your domain code should depend only on your own DTOs and interface. This keeps vendor types out of the domain and makes it easier to replace the integration later.
- Who maintains mpp/universign-bundle and what happens if it is abandoned at the next Symfony major?
- It appears to be an internally extracted component from Mon Petit Placement, a French investment platform, with no public roadmap or community pressure to keep it current. Do not assume a support contract or release cadence unless one is confirmed in writing. The fallback is to call the Universign REST API directly or use an official SDK, so keep the integration behind your own interface to make that migration cheap.