umijs/umi

A framework in react community ✨

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 3rd, 2026
Created on November 22nd, 2017
Open Issues & Pull Requests: 320 (+0)
GitHub issues: Enabled
Number of forks: 2,657
Total Stargazers: 16,040 (+0)
Total Subscribers: 253 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.7 hours
Mean response time: 29.8 days
90th percentile: 53.1 days
Tracked items: 367

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 11% of issues opened in the past year have been closed. Three people close 53% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 129
New in 7 days: 3
Closed in 7 days: 3
Avg open age: 562 days
Stale 30+ days: 123
Stale 90+ days: 120

Recent activity

Opened in 7 days: 2
Closed in 7 days: 3
Comments in 7 days: 4
Events in 7 days: 5

Top labels

  • Need Reproduce (21)
  • type(umi@3) (10)
  • PR Welcome (9)
  • type(enhancement) (8)
  • help wanted (5)
  • type(bug) (5)
  • type(mfsu) (4)
  • type(duplicate) (3)

Most active issues this week

Detailed Description

Umi is a framework in the React community that provides a structured approach to building React applications.

The framework addresses the complexity of setting up and configuring React projects by offering an integrated solution that handles common concerns like routing, state management, and build configuration out of the box. Its approach works by providing conventions and plugins that reduce boilerplate and allow developers to focus on application logic rather than infrastructure setup.

Umi suits teams building medium to large React applications who value convention over configuration and want a batteries-included framework experience. It works well for projects where standardized patterns across the codebase are beneficial. Developers should choose this tool if they prefer a more opinionated framework that handles routing, data fetching, and build optimization automatically rather than assembling these pieces from separate libraries.

The project maintains an active core team with multiple maintainers who have demonstrated sustained engagement through significant contributions addressing issues and implementing features. The maintainer structure includes both core maintainers and a broader group of maintainers who have accumulated substantial merged contributions, indicating a distributed model of ongoing development responsibility. The project operates a contributor recognition system that acknowledges community members with merged pull requests and provides pathways for deeper involvement.