Laravel Splade Jetstream Laravel Package

Product Decisions This Supports

• Build-vs-buy for authentication and account scaffolding. Jetstream is the reference implementation of Laravel's "batteries-included" auth surface: registration, login, password reset, email verification, two-factor auth, profile management, API tokens, and team management. This package answers a narrow question — "do we want that surface rendered with Splade's Blade/Vue single-file-component style instead of Livewire or Inertia?" — and lets you defer hand-building those screens for a first internal or prototype release.
• Frontend stack selection on a new Laravel product. It is effectively a vote for Splade as the view layer. Adopting it means committing your marketing-to-app transition, form handling, and modal flows to Splade's conventions. That is a one-way-ish door on a codebase, so it belongs in the architecture decision record, not in a sprint ticket.
• Time-to-demo for a stakeholder-facing prototype. The realistic use case is a same-day walkthrough of a multi-tenant SaaS shell — teams, invitations, profile settings, 2FA — before you have opinions about design. It compresses a two-to-three-week scaffold into an afternoon, which is genuinely useful for validating scope with stakeholders.
• Reference material for a custom build. Even if you never install it, the repository is a worked example of porting Jetstream's feature set onto a non-standard view layer. That has value to an engineer scoping an in-house equivalent.

What it does not support: any long-lived production decision. It is archived, has 12 stars, zero dependents, and its newest release (1.1.1) explicitly targets Laravel 10 for new projects — now two majors behind current Laravel, and past its own security-fix window. The 0.09 overall score reflects that; the high opportunity score reflects the idea being underserved, not the artifact being healthy.

When to Consider This Package

Consider it only when all of the following hold:

• You are prototyping or building an internal tool where a rewrite in six months is acceptable and expected.
• You have already independently decided to use Splade, so the package is not driving the stack decision.
• You are on Laravel 10 — release 1.1.1 pins new projects there because the Laravel skeleton moved to JS modules — and you have verified the install against your exact Splade version in a throwaway project first.
• A single engineer owns the scaffold and is willing to maintain a fork, because no upstream fixes are coming.

Look elsewhere in every other case, and specifically when:

• You need anything production-grade, multi-year, or audit-relevant (auth and 2FA code carries compliance weight).
• You are on Laravel 11 or later. The 1.1.1 requirement bump is a compatibility floor raise, not a forward-port: it narrows the supported range rather than widening it. An archived scaffolding package is exactly the kind of dependency that silently breaks on a framework upgrade and blocks the upgrade for the whole team.
• You want community support, security patches, or a hiring pool that has seen the stack. Twelve stars and zero dependents means no Stack Overflow answers, no blog posts, and no one to ask.
• You would otherwise have chosen Livewire or Inertia. The standard Jetstream installs are actively maintained and supported; picking a niche view layer to use a niche preset is a bad trade.
• You need SSO, passkeys, or modern MFA. A 2023-era scaffold will not have them.

Practical recommendation: treat this as inspiration, not a dependency. Fork the Blade components you like, or install stock Jetstream and adapt it. If Splade itself is the strategic bet, adopt Splade directly and build the auth screens against it — you will get the same velocity without inheriting an unmaintained bridge. Budget roughly one to two engineer-weeks for that in-house equivalent, which is the honest "buy" price of this package once maintenance risk is priced in.

How to Pitch It (Stakeholders)

To executives: This is a small, MIT-licensed scaffold that generates the standard account, login, two-factor, and team-management screens for a Laravel app, styled with Tailwind. It can accelerate a demo by a couple of weeks. However, it is archived, has essentially no user base, and its latest release only adjusts the required Laravel version — it targets Laravel 10, two majors behind where we build. My recommendation is not to depend on it. For a prototype it saves real calendar time; for anything we intend to run for years, it introduces upgrade and security-maintenance risk that outweighs the savings. The equivalent hand-built scaffold is a one-to-two-week engineering cost — cheap insurance.

To engineering: It is a Jetstream preset that swaps Livewire/Inertia for Splade. The feature surface is the familiar one — registration, password reset, email verification, 2FA, profile, API tokens, teams. Release 1.1.1 is a one-line compatibility change: it requires Laravel 10 for new projects because the Laravel skeleton moved to JS modules. That is a floor on supported versions, not a port to current Laravel, so do not read it as the package coming back to life — it remains archived with zero dependents and no feature work since 2023. It is a fork-and-own proposition, not a dependency, and it forces a Splade commitment we should make explicitly rather than inherit from a scaffolding choice. If Splade is the direction, install Splade and build the Jetstream-equivalent screens ourselves — that is the recommendation I would take to a design review, and the repository is worth skimming as a reference implementation of exactly that port.