logo

microsoft/fluentui

Fluent UI web represents a collection of utilities, React components, and web components for building web applications.

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

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Library / SDKCategory(s):UI Components & Design SystemsFrontend FrameworksWeb Development
Added to GitGenius on September 2nd, 2026
Created on June 6th, 2016
Open Issues & Pull Requests: 808 (+0)
GitHub issues: Enabled
Number of forks: 2,941
Total Stargazers: 20,319 (+0)
Total Subscribers: 288 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.7 hours
Mean response time: 20.5 days
90th percentile: 36.8 days
Tracked items: 1,281

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

29 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 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 83% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "web-components" is answered fastest, typically in about 10 hours, while "Area: Build System" waits about 2 days. 57% of tracked open issues have had no activity in three months. Only 52% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 458
New in 7 days: 3
Closed in 7 days: 2
Avg open age: 703 days
Stale 30+ days: 140
Stale 90+ days: 103

Recent activity

Opened in 7 days: 3
Closed in 7 days: 2
Comments in 7 days: 13
Events in 7 days: 36

Top labels

  • Fluent UI react-components (v9) (836)
  • Type: Bug :bug: (645)
  • Resolution: Soft Close (596)
  • Type: Feature (290)
  • web-components (189)
  • Fluent UI react (v8) (175)
  • Status: In PR (168)
  • Fluent UI WC (v3) (136)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Fluent UI is a collection of utilities, React components, and web components for building web applications that follow Microsoft's design system.

The project addresses the need for consistent, accessible UI components across web platforms by providing three distinct implementations. Fluent UI React v9 represents the forward-looking approach with modern architecture, while v8 offers a mature, production-tested alternative. Web Components provide a framework-agnostic implementation. The repository supports gradual migration between versions, allowing teams to adopt v9 incrementally alongside existing v8 or v0 components rather than requiring a complete rewrite.

Teams should choose Fluent UI if they are building applications that need to align with Microsoft's design language or if they require components used in Microsoft 365, Office, or Edge. The v9 release is the recommended path for new projects, while v8 remains suitable for teams with established codebases. The web components option serves projects that need to work across different JavaScript frameworks or prefer framework-agnostic solutions. Each implementation has separate documentation, changelogs, and npm packages, making it clear which version suits a particular use case.

The project maintains active development across all three tracks with organized issue tracking for each implementation. The repository provides comprehensive documentation and quick-start guides tailored to each variant, reflecting ongoing investment in developer experience. The separation of concerns between v9, v8, and web components suggests deliberate maintenance of multiple maturity levels to serve different adoption scenarios.