vercel/turborepo

Choose this fork only if you need its custom behavior around lockfiles, cache restore, or workspace scanning. If you want current Turborepo releases and the lowest maintenance burden, upstream is the safer choice.

Prefer this fork only if you need its older Turbopack-heavy codebase or a frozen experimental baseline. For normal adoption, upstream Turborepo is the better choice because this fork is stale, heavily diverged, and far behind current fixes and releases.

Prefer upstream unless you specifically need this older, customized baseline. Choose the fork only if its lockfile/example focus matches an internal workflow you are prepared to maintain yourself.

Choose this fork only if you need its specific compatibility or workflow changes and are willing to own a large upstream gap. If you want the latest Turborepo features, fixes, and release cadence, upstream is the safer choice.

Prefer upstream unless you specifically need a private snapshot; this fork shows no added capability and is materially behind a fast-moving project.

Choose this fork only if you need its specific local changes and can tolerate high upstream drift. If you want an actively maintained Turborepo for day-to-day use, upstream is the better fit.

Choose this fork only if you want the older, experimental Turborepo/Turbopack code path and are willing to own long-term maintenance. For adopters who want current Turborepo behavior, this fork is too stale and too divergent.

Choose this fork only if its added workflows are the point. For most adopters, upstream is the safer default because it is much more current and far less divergent.

Choose this fork only if you specifically need its 2025-era snapshot and the lockfile/example coverage it adds. For most adopters, upstream is the better default because this fork is stale and significantly behind on ongoing fixes and releases.