Discofork
Repository brief

laravel/framework

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:30:08.469Z
1mo ago

laravel/framework

Laravel/framework is the core Laravel web application framework repository. It is a very active PHP codebase on the 13.x default branch, with 34,608 stars, 11,816 forks, and recent commits on March 30, 2026. The repository contains the framework source, tests, types, config stubs, and developer tooling, and it is MIT licensed.

GitHub
Loading tags...
Stars34,608
Forks11,816
Default branch13.x
Last pushed2026-03-30T13:33:13Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you specifically need a Laravel 11-derived codebase with its local patches; otherwise upstream Laravel is the better default because it is much newer, actively maintained, and functionally ahead.

Prefer this fork only if you are intentionally staying on a Laravel 5.7-compatible stack. For new work or active platform maintenance, upstream Laravel is the better choice because this fork is materially stale and far behind current framework capabilities.

Choose this fork only if you need an old, customized Laravel branch and are prepared to maintain it yourself. For most adopters, upstream Laravel is the safer and cheaper choice.

Choose this fork only if you already depend on its 11.x-era behavior or its local testing/framework changes. If you want current Laravel compatibility and low-maintenance upgrades, upstream is the better fit.

Prefer this fork only if you need its specific legacy 11.x behavior or custom framework patches. If you want current Laravel maintenance, security fixes, and lower upgrade risk, upstream is the better default.

Choose this fork only if you want a legacy, highly customized Laravel 4.2 branch and are prepared to maintain it yourself. For most adopters, upstream Laravel is the better choice because this fork is stale, deeply divergent, and far behind current framework releases.

Prefer this fork only if you are committed to a legacy Laravel 5.5 stack and need its custom framework behavior. If you want current Laravel features, security fixes, and low-maintenance upgrades, upstream is the better choice.

Prefer this fork only if you need Laravel 11.x with its local patches and you are prepared to maintain a large upstream gap. If you want current Laravel behavior, bugfixes, and ecosystem compatibility, upstream is the better choice.

Choose this fork only if you need its specific local framework changes and are willing to own the maintenance burden. For most users, upstream Laravel is a better default because this fork is far behind and appears stale.

Choose this fork only if you need its custom 10.x-era behavior and are prepared to own a stale, highly divergent framework. If you want current Laravel compatibility and active maintenance, upstream is the better default.