nrwl/nx

The Monorepo Platform that amplifies both developers and AI agents. Nx optimizes your builds, scales your CI, and fixes failed PRs automatically. Ship in...

View on GitHub ↗Jump to charts ↓Open shareable report →

nrwl/nx has 29k+ stars and 3k+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 9 minutes ago
Added to GitGenius on March 4th, 2026
Created on August 11th, 2017
Open Issues & Pull Requests: 476 (+0)
GitHub issues: Enabled
Number of forks: 3,020
Total Stargazers: 29,421 (+0)
Total Subscribers: 219 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.0 days
Mean response time: 38.7 days
90th percentile: 122.0 days
Tracked items: 3,929

Maintainer activity

18 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 5% of issues opened in the past year have never received a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 29% of tracked open issues have had no activity in three months. 73% of issues opened in the past year have been closed, leaving a working backlog. Three people close 50% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 290
New in 7 days: 31
Closed in 7 days: 12
Avg open age: 158 days
Stale 30+ days: 158
Stale 90+ days: 91

Recent activity

Opened in 7 days: 30
Closed in 7 days: 9
Comments in 7 days: 9
Events in 7 days: 32

Top labels

  • outdated (6,396)
  • type: bug (5,420)
  • stale (1,797)
  • scope: core (1,288)
  • priority: medium (1,094)
  • type: feature (656)
  • scope: angular (591)
  • scope: misc (493)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Nx is a monorepo platform that optimizes builds, manages dependencies across multiple projects, and integrates with CI systems to accelerate development workflows.

The tool addresses the complexity of managing multiple interdependent projects within a single repository. Nx constructs a dependency graph of your codebase and uses it to determine which tasks need to run when code changes. It caches build artifacts and test results, skipping work on unchanged code. The core engine is built in Rust for performance while remaining extensible through TypeScript, allowing teams to define custom build steps and generators tailored to their architecture.

Nx suits teams maintaining multiple applications or libraries that share code and need coordinated builds and testing. It works well for polyglot codebases mixing different languages and frameworks. The tool is particularly valuable when CI pipelines become a bottleneck, as it can distribute tasks across machines and leverage remote caching to avoid redundant work. Teams evaluating adoption should expect to invest time in structuring their workspace and defining task dependencies, though the tool provides generators to scaffold new projects and libraries following best practices.

The project maintains a substantial user base, with almost all open issues originating from external adopters reporting real-world problems rather than from the core team. Issue responses typically arrive within one to two weeks. The issue tracker is dominated by bug reports and medium-priority items, with some issues marked as outdated, suggesting the team actively manages the backlog but may not always keep pace with the rate of incoming reports.