Filakit Laravel Package

Product Decisions This Supports

• Build vs. buy for admin scaffolding: filakit is a Filament v3 starter kit — models, resources, and login for user/admin separation. Adopting it buys back roughly days-to-weeks of panel scaffolding; that is a genuine time-to-first-value decision, but it is a starting decision, not an architecture decision. Treat it as a template you fork, not a dependency you inherit.
• Roadmap sequencing for internal tooling: if the roadmap includes an admin back office, a starter kit decouples "we have an admin panel" from "we have a design system." Teams can ship CRUD screens early and revisit polish later — useful when the panel is a means to an end (ops tooling, support console) rather than customer-facing surface.
• Upgrade coupling as a planning input: the release numbering tracks Filament's own (Bump Filament to v3.3.56). Filament v3→v4 will be a hard fork in your dependency graph; any roadmap that assumes "we upgrade Laravel on our schedule" should budget for this kit's maintainer to keep pace — or plan to own the fork.
• Release 3.3.56 specifically: no new features. 24 of 25 merged PRs are dependency bumps, CI workflow standardization, or pnpm overrides for shell-quote / source-map-js. The one substantive item — "Use user/admin packages for models, resources and login" (#197) — is an internal modularization of the kit's own structure. Net PM read: maintenance hygiene, not capability. Do not schedule a re-evaluation or comms on this release; do pin the version and check the diff if you have a fork.
• Supply-chain posture as a decision: the pnpm overrides patching shell-quote and source-map-js are transitive-dependency remediation. That is the maintainer doing the right thing, but it also means your security posture for this package is contingent on one person tracking advisories.

When to Consider This Package

Adopt when:

• You need a Filament v3 admin panel now and the user/admin split + login matches your domain out of the box.
• You intend to vendor/fork it — copy the scaffolding into your app and cut the cord. This is the only posture I'd endorse.
• Your team is small enough that re-deriving a panel from Filament's own docs is a real opportunity cost.
• You can accept a single-maintainer dependency for dev-time scaffolding that never ships in your production runtime code path.

Look elsewhere when:

• You want a runtime dependency you upgrade via composer update forever. Twenty-plus dependabot PRs per release is a signal that this repo is on autopilot for dependency currency, not on a product cadence — a fine trait for a fork source, a poor one for an inherited dependency.
• You are on, or about to move to, Filament v4. The kit's version scheme is welded to Filament v3 minor numbers; there is no evidence of a v4 track.
• Your admin panel is customer-facing or a differentiator. Starter-kit defaults become design debt the moment you have opinions about the UX.
• You need a support contract, security disclosures with SLAs, or a bus factor above one. Sponsorship links (FUNDING.yml, Buy Me a Coffee) were added in this release — the maintainer is signaling sustainability intent, but that isn't the same as sustainability guarantee.
• Your org requires dependency provenance review. Every bump in this release is automated; nobody is hand-reviewing whether vite 8.3.0 → 8.3.1 interacts with your build.

Gate to put on adoption regardless: a 30-minute read of composer.json and the User/Admin model split to confirm it matches your auth model — "user/admin packages" in #197 means the auth surface is opinionated and will be the first thing you fight.

How to Pitch It (Stakeholders)

To executives: This is a free, open-source Laravel starter kit for admin back-office screens. It saves us the setup cost of an internal panel — realistically a few days of engineering — at the cost of a dependency on a single independent maintainer. My recommendation is to use it as a template we copy once and then own, not as a component we depend on indefinitely. That converts a support risk into a one-time time saving, which is the right trade. No budget, no procurement, no vendor negotiation required.

To engineering: Filament v3 scaffold with user/admin separation, resource and login generation. Release 3.3.56 is a maintenance drop — dependency bumps, CI standardization, transitive vulnerability patches via pnpm overrides, and one internal refactor moving models/resources/login into separate packages. No API surface to learn, no migration required. Use it as a laravel new-style starting point, commit the output, and remove the package from require. If you keep it as a live dependency instead, budget for a Filament v3→v4 migration you don't control the timing of.

The honest caveat to state once, internally: the release cadence here is dependabot plus CI chores. That's competent housekeeping and a fine signal for a scaffolding source. It is not evidence of an active feature roadmap, and nobody should plan around this kit gaining capabilities.