Awesome Open Source logo
Awesome Open Source
Sign in Create account

microsoft/fast

The adaptive interface system for modern web experiences.

9,665
Stars
over 8 years
Age
0
Published reviews
0
Questions

Reliability breakdown

What drives the reliability score

Component scores measured daily from GitHub activity (2026-02-26).

Continuity30% of headline11

Activity on 0 of 40 tracked days in the last 90 and 0 of 27 in the last 30.

Activity pulse
Closure30% of headline0

Merged 0 of 0 PRs opened and closed 0 of 0 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.

PRs merged (90d)PRs opened (90d)Issues closed (90d)Issues opened (90d)
Shipping20% of headline0

0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 — a steady cadence scores highest.

Releases
Liveness10% of headline100

Last push 4 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).

Repository
Support burden10% of headline15

Open-issue load isn't tracked for this repo yet.

Open issuesStargazers
Adoption confidence2

Modeled — how confidently teams are adopting this repo. Stargazers

Maintenance quality4

Modeled from PR/issue responsiveness and upkeep signals. Activity pulse

Risk score98

Modeled — lower is better; adoption and continuity risk. Repository

Stays active (30d)0%

Modeled chance the repo stays active over 30 days. Activity pulse

Stays active (90d)5%

Modeled chance the repo stays active over 90 days. Activity pulse

Release rhythm (180d)0

Regularity of releases over the last 180 days. Releases

Maintainer bus risk (90d)90%

Modeled — lower is better; concentration of commits in few maintainers. Contributors graph

Topics

Explore related topics

Jump into the topic listings this repository belongs to.

Development ToolsReactWebWeb ComponentsWeb Accessibility

Measured history

Project metrics

Weekly GitHub totals with 30, 90, and 180 day views.

Issues opened

Feb 22, 2026

Current0

Previous0

Weekly total

110
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

36 observed daily rows. Missing days are not fabricated.

DateValue

Issues closed

Feb 22, 2026

Current0

Previous0

Weekly total

110
Full metrics details

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

36 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests opened

Feb 22, 2026

Current0

Previous0

Weekly total

110
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

36 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests closed

Feb 22, 2026

Current0

Previous0

Weekly total

110
Full metrics details

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

36 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests merged

Feb 22, 2026

Current0

Previous0

Weekly total

110
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

36 observed daily rows. Missing days are not fabricated.

DateValue

About Fast

<p>Microsoft FAST is a design system and web component ecosystem that emphasizes performance, standards-based architecture, and scalable theming. Although FAST is framework-agnostic at its core, it integrates well with React projects that need reusable UI foundations across multiple front-end stacks. The component model is built for long-term portability, making it attractive in organizations with mixed technology surfaces.</p>
<p>FAST is a strong fit when design consistency must span more than one framework or runtime. Its token-driven styling model and composable primitives support enterprise branding and accessibility requirements without locking teams into a single rendering layer. For platform teams, FAST can serve as a durable UI substrate while product teams consume components in React with predictable behavior.</p>

Join the conversation

Reviews · Questions · Posts

Share what you know about fast — write a review from your real experience, ask an implementation question, or publish a post about how you use it.

Write a review Ask a question Write a post

Share your experience

Write or update your review

Explain what worked, what broke down, and what another team should know before adopting fast.

Sign in to review Create account

Write your review now — it saves locally and publishes automatically after you sign in.

Rating
Positive attributes
Negative attributes

Project Q&A

Questions and answers

Browse implementation threads tied directly to microsoft/fast. Each question links through to the full answer page.

Q&A No threads yet

Be the first to ask how teams run fast in production. Every question you post becomes a durable, searchable answer page other developers can find.

Ask the first question

Related posts

Posts tagged with the same topics

These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.

Posts No topic-linked posts yet

Share how your team uses fast — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.

Write the first post
Get a weekly email with the hottest new projects in the React and Component Library world.
No Spam. Unsubscribe easily at any time.
Privacy | About | Terms | Follow Us On Twitter

Copyright 2018-2026 Awesome Open Source.  All rights reserved.