Discofork
Repository brief

vercel/Next.js

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-06-11T17:19:46.267Z
4w ago

vercel/Next.js

vercel/next.js is a large, active monorepo for Next.js, described as "The React Framework." It is not archived, has very high adoption signals (139,919 stars and 31,211 forks), and was updated and pushed on June 11, 2026. For fork interest, this is a broad, fast-moving upstream with many package boundaries and multiple implementation surfaces, so forks are most likely useful when they want to diverge on framework behavior, tooling, or internal platform integration rather than stay lightweight.

GitHub
Loading tags...
Stars139,919
Forks31,211
Default branchcanary
Last pushed2026-06-11T16:51:10Z
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 Module Federation on Webpack 5 is the primary requirement and you are prepared to own an aging, highly divergent Next.js codebase. For most adopters who want current Next.js features and lower maintenance risk, upstream is the safer default.

Choose this fork only if you need a long-lived custom Next.js branch and are prepared to own substantial maintenance. If your goal is to consume current Next.js behavior with minimal divergence, upstream is the better fit.

Prefer this fork only if you need the embedded SuperTokens-oriented customization or other framework-level changes enough to justify carrying a stale, highly divergent Next.js branch. If you want current Next.js behavior, upstream is the safer choice because this fork is far behind and will be expensive to maintain.

Choose this fork only if you need a bespoke Next.js variant and are prepared to maintain a large divergence. If your priority is staying current with upstream Next.js features and fixes, upstream is the safer default.

Choose this fork only if you need its custom workflow or experimental changes and are prepared to maintain a large, stale divergence yourself. If your goal is to track modern Next.js behavior, this fork is a poor fit because it is far behind upstream and shows signs of heavy local customization.

Prefer this fork only if you need the specific local changes and are willing to own ongoing upstream integration. If you want the latest Next.js features, bugfixes, and lower maintenance cost, upstream is the better choice.

Adopt this fork only if you need the custom runtime or framework behavior it provides and you are willing to own a substantial divergence from upstream. For most teams, the stale cadence and 200-commit gap make upstream Next.js the safer default.

Choose this fork only if you need its custom internal workflow or experimentation surface and are prepared to maintain a large delta from upstream. If you want a current, broadly supported Next.js base with lower operational risk, upstream is the better choice.

Prefer this fork only if you explicitly want an older, customized Next.js codebase with extra repo/workflow automation and you are prepared to own a large maintenance gap. If your goal is to adopt modern Next.js capabilities, the active upstream is the better choice.

Choose this fork only if you need to modify Next.js internals or integrate it tightly with your own platform and are prepared to maintain a large upstream delta. If you mainly want standard Next.js features and fast access to fixes, upstream is the safer choice.

vercel/Next.js · Discofork