/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

vercel/turborepo

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-30T19:48:14.385Z

1mo ago

vercel/turborepo

vercel/turborepo is an actively maintained, popular monorepo build system for JavaScript and TypeScript, implemented in Rust. It has a large footprint (about 30k stars, 2.3k forks) and very recent activity, including 2.9.0/2.9.1-canary releases on March 30, 2026. Forks are likely most interesting if you care about build tooling, workspace orchestration, or Rust-backed performance work in JS/TS ecosystems.

Loading tags...

Stars30,089

Forks2,307

Default branchmain

Last pushed2026-03-30T19:42:32Z

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

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream unless you specifically need the older Turbopack-inclusive fork or want a research base. For production adoption, the fork looks too stale and too far behind current Turborepo maintenance to be the safer choice.

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.

Fork comparison

yyx990803/turbo

38/100

stale

significant_divergence

Prefer upstream unless you specifically need the older Turbopack-inclusive fork or want a research base. For production adoption, the fork looks too stale and too far behind current Turborepo maintenance to be the safer choice.

Likely purpose

A historical fork for teams exploring both Turborepo and Turbopack in a Rust-based JavaScript/TypeScript toolchain, likely for experimentation rather than day-to-day adoption of current upstream Turborepo.

Best for

Engineers who want to study or revive an older Turborepo/Turbopack codebase.; Teams building experimental tooling around bundling plus monorepo orchestration.; Contributors comfortable maintaining a heavily diverged fork themselves.

Additional features

Includes Turbopack alongside Turborepo, broadening it from a monorepo build system into a bundler-plus-build-tooling fork.
Appears to preserve or extend lockfile and package-manager testing around pnpm/npm workflows, which suggests more emphasis on package-management edge cases.
Carries a larger, older snapshot of the workspace that may be useful if someone wants to study or build on the 2022-era codebase rather than current upstream behavior.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.

Missing features

Misses roughly 200 upstream commits of recent work, including current release and canary activity.
Lacks recent upstream fixes such as package-manager catalog migration support, reduced inotify watch usage on Linux, and symlink-related workspace/cache handling improvements.
Is materially behind the actively maintained upstream Turborepo release train, so current docs, bugfixes, and maintenance workflow are not present here.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Broader scope than upstream by combining bundler and build-system concerns.
Could be useful for research, forking, or backporting ideas from an older codebase snapshot.
Still has some community traction despite being very stale.

Risks

Very stale relative to upstream activity.
Large structural divergence makes rebasing or cherry-picking from upstream costly.
Adopters may inherit old bugs and outdated assumptions about package managers and workspace discovery.