Filament Modular Luncher Laravel Package

Product Decisions This Supports

• Build vs. buy for module administration: Supports buying/adopting a Filament-native module control center instead of building custom admin screens for Laravel Modular lifecycle management.
• Modular architecture investment: Justifies adopting or standardizing on Laravel Modular ^1.2 by pairing it with operational tooling for health, diagnostics, metadata, and controlled installation.
• Internal developer platform roadmap: Health badges and diagnostic actions (Module Doctor, Status Report, Debug JSON, Explain Module) map directly to internal platform/SRE workflows and support runbooks.
• Security and governance policy: First-class Git installs, Composer validation, vendor allowlists, and remote URL host allowlists inform decisions about whether module installs are permitted in local, staging, or production-adjacent environments.
• Third-party/plugin ecosystem readiness: Ecosystem metadata visibility (requires, conflicts, provides, middleware, policies, events) supports decisions about exposing modules to other teams or customers.
• Operational risk reduction: v1.1.0 hardens Composer/Git execution, ZIP extraction, URL installs, and secret redaction—lowering the risk of exposing a module management UI to broader internal users.

When to Consider This Package

Consider this package when:

• You are using Laravel Modular ^1.2 and Filament, and need an admin-facing module control center.
• You want module health visibility (healthy, disabled, dependency review, conflicts) without building custom dashboards.
• You need diagnostic actions such as Module Doctor, Status Report, Debug JSON, and Explain Module for support and onboarding.
• You want controlled install paths across Git, ZIP, URL, and Composer with validation and allowlists.
• You value tested compatibility with Laravel 12/13, PHP 8.3–8.5, and CI-backed quality checks (Pest, Pint, PHPStan).
• You are an agency, platform team, or SaaS operator maintaining many modules and needing safer operational tooling.

Look elsewhere when:

• You are not using Filament or Laravel Modular.
• You need a public marketplace with billing, licensing, or customer-facing plugin distribution.
• You require enterprise-grade RBAC, full audit trails, SSO, or vendor SLA support beyond Filament defaults.
• You cannot allow UI-driven module installation in any environment.
• You are on older Laravel/PHP versions outside the supported matrix.
• You have a small single-app codebase where module management overhead exceeds the benefit.

How to Pitch It (Stakeholders)

For executives: This package gives our Laravel admin a ready-made module control center, reducing bespoke admin development while improving governance over how modules are installed, validated, and monitored. The v1.1.0 security hardening—safe process execution, ZIP traversal protection, URL validation, and secret redaction—makes it safer to expose module management to internal operators.

For engineering: It is a Filament-native UI over Laravel Modular ^1.2 with module health badges, diagnostic actions, ecosystem metadata visibility, and controlled Git/ZIP/URL/Composer installs. It includes Composer validation, vendor and host allowlists, Laravel Boost guidance, and CI coverage across Laravel 12/13 and PHP 8.3–8.5 with PHPStan and Pint.

For stakeholders: Adopt it to shorten internal tooling delivery, improve module troubleshooting, and reduce the risk of unmanaged third-party module onboarding—without committing to a custom admin build.