laravel/jetstream

Tailwind scaffolding for the Laravel framework.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 17th, 2026
Created on August 31st, 2020
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 826
Total Stargazers: 4,061 (+0)
Total Subscribers: 97 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.5 hours
Mean response time: 7.8 days
90th percentile: 19.7 days
Tracked items: 31

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 329 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (3)
  • needs more info (3)
  • enhancement (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Jetstream is a scaffolding package for the Laravel framework that provides pre-built authentication and application structure using Tailwind CSS.

Jetstream solves the problem of repetitive setup work when starting a new Laravel project. Rather than building authentication flows, user management, and UI components from scratch, developers receive a complete foundation with login, registration, password reset, and team management features already implemented. The package generates boilerplate code and views styled with Tailwind CSS, allowing teams to begin building application-specific features immediately instead of handling common infrastructure concerns.

Jetstream suits teams building web applications with Laravel who want to skip the initial scaffolding phase and adopt a consistent, modern design system from the start. It works best for projects where the default authentication model and team structure align with requirements, since customizing heavily scaffolded code can become complex. Developers working on APIs or applications with highly specialized authentication needs may find the opinionated structure constraining and prefer building authentication layers independently.

The project maintains steady activity with regular updates to keep pace with Laravel and Tailwind CSS releases. Pull requests receive timely review and merging, indicating active maintenance. Issues are addressed consistently, showing responsiveness to reported problems and feature requests. The codebase reflects ongoing refinement rather than dormancy, with commits addressing both bug fixes and incremental improvements to the scaffolding templates.