- What is the mfakitv5 package and what does it actually include?
- MFAKit is a Laravel starter kit built on Filament 5.x that ships a pre-wired admin panel with multi-factor authentication already integrated. It supports TOTP authenticator apps, email codes, and WhatsApp verification as second factors. As of 5.9.0 the User and Admin models, Filament resources, and login flow live in dedicated packages rather than app-local code. It is a scaffold you generate a project from, not a drop-in library.
- How do I install mfakitv5 in a new Laravel project?
- Use Composer create-project against the repository, or clone it and run composer install, then complete the standard Laravel setup: copy .env, generate the application key, run migrations, and build assets with Vite. Because it is a starter kit, the generated application code ends up in your own project after installation. Check composer.json first for the exact PHP, Laravel, and Filament constraints before committing.
- Which Laravel and PHP versions does mfakitv5 support?
- The package targets Laravel 13.x with Filament 5.x and a PHP 8.2+ baseline, and its own CI includes a PHPStan job running on PHP 8.4. The 5.9.0 release notes do not explicitly restate minimum PHP or Laravel versions, so composer.json is the authoritative source. On older Laravel majors, pin carefully and expect dependency conflicts.
- What multi-factor authentication methods does MFAKit support?
- MFAKit supports three second factors: TOTP codes from authenticator apps, email-delivered verification codes, and WhatsApp messages. That gives users a fallback path if they lose their authenticator device. Configuration lives in the package config and the package-provided login flow, so the available methods are wired in before you customize anything.
- Can I add mfakitv5 to an existing Laravel app with composer require?
- No, it is a starter kit and application scaffold rather than a library you require into a running app. You generate a project from it and then own the resulting code, which means upgrades are diffs against your customized tree instead of clean vendor bumps. If you need MFA in an existing Laravel application, pairing Fortify or a dedicated MFA package with Filament is usually the better fit.
- What changed in mfakitv5 5.9.0 and does it break my fork?
- 5.9.0 bumps the underlying Filament to 5.9.0 and, through PR 79, moves the User and Admin models, Filament resources, and login flow into dedicated packages instead of app-local code. That is a structural refactor shipped in a minor release, so anyone pinned to ^5.8 will absorb it silently, which is a semver tension worth noting. If you customized those exact files, expect conflicts; no migration guide is published in the release notes.
- How do I upgrade an existing mfakitv5 project from 5.8.x to 5.9.0?
- Treat it as a re-scaffold rather than an in-place upgrade. Pin to 5.8.4, diff your generated tree against a fresh 5.9.0 scaffold, and focus on the User and Admin models, Filament resources, and login flow, since those are the surfaces moved by PR 79. Rebase your customizations onto the package-provided classes or explicitly override them, then regenerate the admin panel and re-run auth smoke tests before merging.
- Is mfakitv5 compatible with other Filament plugins like Shield and Spatie permissions?
- It should be, provided each plugin declares support for Filament 5.9.0, because the starter kit now inherits Filament's deprecations and constraints. Plugin drift across Shield, Spatie permissions, and media library packages is the most common failure point after a Filament bump. Verify constraints before upgrading and avoid landing the starter kit bump and a plugin upgrade in the same sprint.
- What are the alternatives to mfakitv5 for MFA in Laravel?
- Laravel Fortify and Jetstream provide first-party two-factor authentication without the Filament scaffolding, which suits apps that already have an admin UI. Dedicated MFA packages give you TOTP or email verification as a Composer dependency you can require into an existing codebase. mfakitv5 only makes sense if you specifically want a Filament 5 admin panel plus TOTP, email, and WhatsApp factors generated for you in one step.
- Is mfakitv5 production-ready and actively maintained?
- It is actively maintained: 5.9.0 includes dependabot updates, standardized changelog and test workflows, PHPStan on PHP 8.4, and routine dependency bumps. The technical risk is moderate rather than low, because the package-extraction refactor landed in a minor version with no published migration path and no stated coverage numbers for the new package-based auth flow. It is a sound scaffold for greenfield Filament admin panels, but brownfield adopters should budget reconciliation time.