Turborepo is a build system for JavaScript and TypeScript monorepos, written in Rust and released under the MIT licence, intended for teams that build many packages inside one repository and for the coding agents those teams run against it.

What it is

Turborepo is an open-source build system for JavaScript and TypeScript codebases, tagged in this registry as a build system, a build tool, and a monorepo tool. It is written in Rust and lives in the vercel organisation on GitHub, where the README describes it in a single line as "the build system for coding agents." The project carries 31,093 stars and 2,444 forks, and it has been pushed to as recently as 16 September 2026. Its public face for documentation and onboarding is the homepage at https://turborepo.dev.

The problem it addresses is the build layer of a monorepo. In a JavaScript or TypeScript repository that holds many packages, each workspace ordinarily carries its own scripts and its own build step, and the work of coordinating them falls on hand-written configuration. Turborepo occupies that orchestration slot: it is the tool a monorepo leans on instead of wiring each package's build, test, and lint scripts together by hand. Because the engine is written in Rust while the code it builds is JavaScript and TypeScript, the project sits deliberately across two ecosystems — a native implementation serving a JavaScript toolchain.

Key capabilities

• Monorepo build orchestration: the topic list marks the project as both a build system and a monorepo tool, so its unit of work is the repository rather than a single package.
• JavaScript and TypeScript support: both languages appear explicitly in the topic list and in the project description.
• Rust implementation: the engine is written in Rust, which the repository language field confirms.
• Documentation and onboarding at https://turborepo.dev, named in the README as the place to get started.
• Community channels: GitHub Discussions for questions, ideas, and project sharing, plus the #turborepo tag on Vercel Community for chat.
• Contribution path through CONTRIBUTING.md, with the Code of Conduct applying to every Turborepo community channel.
• Coordinated security disclosure: vulnerabilities go to [email protected] rather than a public issue, with policy at https://security.vercel.com/.

Who uses it and how

• Development teams building JavaScript and TypeScript monorepos, the shape the tool is designed around.
• Organisations showcased publicly: the README states that Turborepo is used by leading companies and points to the Turborepo Showcase at https://turborepo.dev/showcase for the list.
• Coding agents, which the README names as the audience for the build system in its opening line.
• Contributors working against CONTRIBUTING.md, with discussion routed through GitHub Discussions and updates posted via @turborepo on X.
• Security researchers using the private email channel rather than the issue tracker, which currently holds 13 open issues.

Getting started

Getting started is handled off-repository: the README directs readers to https://turborepo.dev for installation and first-run instructions, and the repository itself ships no install command in its README.

How it compares

No competing or paid products are named in the available facts, and no alternative tools are listed either. On the evidence here, Turborepo stands alone in this registry.

When to use it — and when not to

This page is built from a deliberately sparse README, so a self-hoster gets no in-repository instructions for dependencies, caching infrastructure, or environment setup, and must rely on https://turborepo.dev and the community channels for anything beyond contribution and security policy. Teams outside JavaScript and TypeScript, or working in single-package repositories rather than monorepos, are not the audience the topics and description describe. Weigh the low open-issue count and recent push against the thin README before adopting it as a documented dependency.