Repo brief: vercel/turborepo

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T00:45:37.947Z · commit 4b3e7cc96d13

Verdict

Healthy — Strong maintenance signals

• Last commit today
• 10 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Turborepo is a high-performance build system for JavaScript and TypeScript monorepos, written entirely in Rust. It optimizes task execution across multiple packages by intelligently caching outputs, parallelizing tasks, and deduplicating work—solving the slow, redundant builds endemic to large JavaScript monorepos like those at Vercel and other enterprises. Monorepo with Rust crates under crates/ (turborepo-engine handles orchestration, turborepo-cache for artifact storage, turborepo-daemon for persistent state, turborepo-auth/turborepo-api-client for Vercel integration) and TypeScript packages under packages/ for CLI and docs. Workspace config (Cargo.toml) declares 2024 edition Rust with…

Start here

Open these first:

• Cargo.toml — Root workspace configuration defining all Rust crates, profiles, and workspace dependencies that every Rust contributor…
• .github/workflows/turborepo-test.yml — Primary CI/CD pipeline for testing the Rust codebase; understanding test automation is essential for PR contributions.
• .github/actions/setup-rust/action.yml — Rust toolchain setup and configuration shared across all workflows; critical for local development environment alignment.
• .config/nextest.toml — Test runner configuration that defines how the entire Rust test suite executes; required for understanding test…
• CONTRIBUTING.md — Development guidelines and contribution workflow for the entire turborepo project; must-read before opening PRs.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/vercel/turborepo.git
cd turborepo
cargo build --release
cargo test

Requires Rust (1.70+), Node.js, and optionally Cap'n Proto for schema changes. See CONTRIBUTING.md for full setup.

Daily commands:

# Build Rust core
cargo build --release

# Run tests
cargo test -p turborepo

# Build TypeScript packages
cd packages/turbo-repository && npm install && npm run build

# For LSP development
cargo build --release-turborepo-lsp

Check .github/workflows/turborepo-test.yml and Makefile for CI test commands.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 64% of recent commits
• Cap'n Proto requirement: Schema changes in .proto files require capnproto toolchain (setup via .github/actions/setup-capnproto/); omitting this breaks builds. Daemon state: turborepo-daemon may leave stale…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.