fork intelligence · vercel/next.js

What’s living in vercel/next.js’s forks?

The React Framework Scanned 31,771 forks, 40 inspected in depth, 4 carrying real unmerged work.

forksplorer.com/repo/vercel/next.jscached scan · 2026-08-23

▲ scanned vercel/next.js — 31,771 forks · 40 inspected · 4 features surfaced

#1 Update with-supertokens example supertokens/next.js · 5 ahead · last push 2024-06-13

196fb03 Update with-supertokens example — anku255 5423891 updates to latest version of supertokens' sdks — rishabhpoddar $ git cherry-pick 5423891^..196fb03 → view fork on GitHub

#2 Changed gitignore and removed netlify.toml lfades/next.js · 14 ahead · last push 2025-01-09

1eaac97 Changed gitignore and removed netlify.toml — Luis Alvarez 97c644f Removed the takeshape provider and api pages — Luis Alvarez 7f03b94 updated post item — Luis Alvarez 01ffba3 update posts components — Luis Alvarez 6ffb804 Updated author page — Luis Alvarez $ git cherry-pick 6ffb804^..1eaac97 → view fork on GitHub

#3 Don't terminate PPR renders with dynamicUsageErr sebmarkbage/next.js · 1 ahead · last push 2025-10-21

07c5fdc Don't terminate PPR renders with dynamicUsageErr — sebmarkbage $ git cherry-pick 07c5fdc → view fork on GitHub

#4 Build next-swc binaries timneutkens/next.js · 3 ahead · last push 2023-08-26

21bae2b Build next-swc binaries — timneutkens 25fa32f Build next-swc binaries — timneutkens $ git cherry-pick 25fa32f^..21bae2b → view fork on GitHub

$

View vercel/next.js on GitHub · Cached scans refresh weekly — not a live per-request re-scan.