- What is jeffersongoncalves/evolutionkitv4 used for?
- It is a Laravel 13 and Filament 4 starter kit for WhatsApp integration through Evolution API v4. It provides the admin-side domain for managing instances, contacts, messaging, and webhooks. Treat it as an application scaffold for internal ops or support tooling, not as a reusable library you drop into a shared codebase.
- How do I install and configure evolutionkitv4?
- Install it into a fresh Laravel 13 application with Filament 4 rather than into a shared package codebase. Require an exact tag such as 4.14.0 in composer.json, publish the package migrations and config, and configure your Evolution API endpoint and credentials. Because 4.14.0 moved models, resources, and login into user/admin packages, review those dependencies and namespaces before running migrations.
- What Laravel, PHP, and Filament versions does evolutionkitv4 require?
- The kit targets Laravel 13.x and Filament 4.x, and its CI runs PHPStan on PHP 8.4. The available evaluation treats a Filament 3 or PHP 8.2/8.3 estate as a hard stop. Confirm the exact PHP, Laravel, Filament, and Node/Vite versions in composer.json and package.json before committing.
- Can I add evolutionkitv4 to an existing Filament panel or auth system?
- No, it is an application kit that presumes it owns the panel, the User and Admin models, and the auth flow. That makes it a poor fit for bolting onto an existing Filament panel or an existing authorization model. Use it for greenfield internal admin or support consoles instead.
- What changed in evolutionkitv4 4.14.0, and is it a breaking change?
- Version 4.14.0 switches to user/admin packages for models, resources, and login, externalizing those extension points. That changes the migration and seed surface, class namespaces, and the classes you would extend or override. The release notes reportedly lack an upgrade guide, so treat it as breaking for any 4.13.x deployment and diff namespaces and published migrations carefully.
- Does the evolutionkitv4 version number follow the package API or Filament releases?
- The available evaluation says the package's versioning appears to track Filament's release line, with 4.13.x to 4.14.0 landing alongside a Filament v4.14.0 bump. That means the version number is not a reliable contract for this package's own API surface. Pin exact tags and vet upgrades as change requests rather than floating a ^4 constraint.
- Does evolutionkitv4 include the Evolution API client, or only the admin UI?
- The package description says it provides typed clients, configuration helpers, and Laravel-friendly service bindings, but the evaluation flags the client-versus-UI boundary as something to verify. Deployment still requires a reachable Evolution API endpoint and its database. Check composer dependencies and the source for an HTTP client before assuming it replaces a separate Evolution API deployment.
- How do I test Evolution API webhooks and messages locally with evolutionkitv4?
- The kit includes webhook handling as part of its WhatsApp domain, but the available notes do not document a dedicated testing harness. Expose your Laravel app through a tunnel and point the Evolution API webhook at it, then assert stored records or dispatched jobs. Use Laravel HTTP tests and queue fakes around your own handlers, and confirm whether the package ships webhook signature verification before relying on it.
- Is evolutionkitv4 actively maintained and suitable for production?
- It is a single-maintainer, early-adoption project with a bus factor of one and no visible downstream usage in the available data. That does not make it unusable for internal tooling, but it does argue for pinning an exact tag, reviewing migrations, and keeping an exit path. Alternatives include integrating Evolution API directly with your own typed HTTP client or choosing a more established Laravel WhatsApp package that documents its Filament and Laravel support.
- What license does evolutionkitv4 use, and is commercial use allowed?
- The available notes do not state a license, and the evaluation flags license and commercial-use terms as an open question. Check the repository LICENSE file and composer.json license field before using it commercially or redistributing it. Do not assume MIT or another permissive license until you confirm it.