Basev3 Laravel Package

Product Decisions This Supports

• Build vs. buy for back-office tooling. filakitphp/basev3 is a Laravel + Filament v3 starter kit (admin panel, user model, user resource, login) rather than a product. The decision it informs is "do we scaffold our internal admin on this baseline, or pay for Retool/Metabase-style tooling, or build the auth + CRUD layer ourselves?" This release (3.3.56) keeps that baseline current with upstream Filament 3.3.56, so the baseline stays a live option rather than a stale fork.
• Time-to-first-value for internal tools / MVP admin surfaces. The value proposition is days-not-weeks for CRUD screens, auth, and user management. That maps directly to roadmap sequencing: which internal tools ship this quarter vs. next.
• Standardization decision. Adopting one baseline across multiple internal apps (same auth, same panel conventions, same CI) is a platform bet. This release moves the repo toward that: standardized Dependabot config, standardized test and changelog workflows, and PHPStan running on PHP 8.4 — i.e. the project is investing in repeatable CI, which is the thing you actually inherit when you standardize.
• Runtime and toolchain baselines. Two changes here are quietly product-relevant: CI now exercises PHP 8.4, and the front-end build migrated from pnpm to bun. Both constrain your hosting image and developer onboarding docs, so they belong in the platform decision, not just the dev backlog.
• User-layer ownership. The switch to filament-user for the user model, resource, and login means the identity layer is now an external package rather than in-repo code. For a PM this is a "who owns user management, and what's our exit cost?" question — it simplifies upgrades but adds a dependency on your critical path.
• Dependency currency as a risk metric. 13 of 16 changes in this release are Dependabot bumps. Useful signal: the project has automated dependency hygiene, which lowers the security-patch lag you'd otherwise absorb when self-maintaining a starter kit.

When to Consider This Package

Consider it when:

• You are starting a Laravel back office / admin panel and want Filament 3 with auth, user model, and user CRUD already wired.
• Your team is already on Laravel + Filament and wants a conventional starting point instead of a greenfield scaffold.
• You want CI hygiene (PHPStan, standardized workflows, automated dependency updates) inherited rather than authored.
• You need a fast internal-tool MVP where the admin surface is a means to an end, not the product.
• Your runtime can target modern PHP (8.3/8.4) and you are comfortable with a bun-based front-end build.

Look elsewhere when:

• You need Filament v4 or a roadmap beyond the 3.3.x line — this release is a pin, not a forward migration.
• You are upgrading an existing fork. Two changes are upgrade hazards, not features: the user model/resource/login now come from filament-user, and the asset build moved from pnpm to bun. Any existing customization of the user layer or any CI/deploy script invoking pnpm will need rework.
• You need vendor-backed SLAs, LTS guarantees, or a formal deprecation policy. This is a community starter kit whose version numbers track upstream Filament, so "3.3.56" tells you about Filament's release, not about this repo's own API stability.
• Your product is API-first/headless and does not need a server-rendered admin panel.
• You expect deep, atypical customization of auth or the panel — you would be fighting the scaffold, and the filament-user indirection adds a layer to override.
• Compliance or procurement requires a documented security review cadence rather than bot-driven bumps.

Upgrade note for this specific release: treat 3.3.56 as low-risk for a clean install and medium-risk for an existing project, purely because of the user-layer swap and the pnpm→bun tooling change. Everything else is patch-level dependency maintenance and CI configuration.

How to Pitch It (Stakeholders)

For executives: This is a free, open-source starting point for the internal admin screens behind our product — user management, login, and CRUD tables. Adopting it compresses the build of an internal tool from weeks to days and shifts our spend from writing boilerplate to customizing what actually differentiates us. The cost is not licensing; it is engineering time to customize and the ongoing cost of tracking an open-source dependency. The 3.3.56 release shows that cost is currently being absorbed well: the project automated its dependency updates and hardened its test pipeline, which is exactly the maintenance burden we would otherwise own ourselves.

For engineering: 3.3.56 is a pin to Filament 3.3.56 plus maintenance. No new features; no intentional breaking changes. Three things to check before adopting or upgrading: (1) the user model, user resource, and login now come from the filament-user package — verify your auth customizations survive; (2) the front-end build moved from pnpm to bun — any CI or deploy step calling pnpm needs updating; (3) PHPStan now runs against PHP 8.4, so your runtime baseline should match. Upside: standardized workflows and Dependabot config reduce the chance we inherit a stale, hand-maintained scaffold. Recommendation is to adopt on greenfield internal tools, and to treat upgrades on existing forks as a small, scoped migration task rather than a routine version bump.