microsoft/rushstack

Monorepo for tools developed by the Rush Stack community

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 10th, 2026
Created on September 30th, 2016
Open Issues & Pull Requests: 1,095 (+0)
GitHub issues: Enabled
Number of forks: 708
Total Stargazers: 6,495 (+0)
Total Subscribers: 50 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.3 days
Mean response time: 34.0 days
90th percentile: 38.1 days
Tracked items: 334

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "enhancement" is answered fastest, typically in about 9 hours, while "effort: medium" waits about 5 days. 56% of tracked open issues have had no activity in three months. Only 5% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 221
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 604 days
Stale 30+ days: 205
Stale 90+ days: 172

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (31)
  • effort: easy (26)
  • enhancement (26)
  • bug (17)
  • effort: medium (13)
  • area:rushd (8)
  • needs design (8)
  • repro confirmed (8)

Detailed Description

Rush Stack is a monorepo for build tooling and orchestration designed for large-scale TypeScript projects.

The project addresses the complexity of managing dependencies, builds, and API documentation across multiple interconnected TypeScript packages. It provides an integrated ecosystem where Rush serves as a build orchestrator that coordinates work across monorepo packages, Heft handles individual project builds and toolchain integration, API Extractor generates TypeScript declaration rollups and tracks API surface changes, and TSDoc establishes a standard for documentation comments. Lockfile Explorer helps diagnose and resolve version conflicts in package manager lockfiles, while API Documenter converts TSDoc comments into published API reference sites.

Teams managing large TypeScript monorepos should consider Rush Stack when they need coordinated builds across many packages, want to enforce consistent tooling and API contracts, or need to track breaking changes in their public APIs. The ecosystem is particularly suited to organizations publishing multiple related NPM packages where API stability matters. The project explicitly positions itself as a mission-driven collection of reusable tools rather than a single monolithic solution, allowing teams to adopt individual components like API Extractor or TSDoc independently without committing to the entire stack.

The project maintains active engagement with its community through a dedicated Zulip chat room for developer discussion. Development activity shows consistent attention to the codebase with regular updates across multiple tool components. The monorepo structure itself serves as a working example of the patterns and practices the tooling is designed to support, demonstrating the orchestration and build coordination capabilities in a production setting.