Build and document UI components in isolation

Storybook gives JavaScript teams a focused workspace for developing, testing, and showcasing UI components.

90,625
Stars
over 10 years
Age
0
Published reviews
0
Questions

Reliability breakdown

What drives the reliability score

Component scores measured daily from GitHub activity (2026-07-15).

Continuity30% of headline85

Activity on 84 of 90 tracked days in the last 90 and 26 of 30 in the last 30.

Closure30% of headline78

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

Shipping20% of headline100

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

Liveness10% of headline100

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

Support burden10% of headline65

1,577 open issues against 90,625 stars — about 17 open issues per 1,000 stars. Lighter backlogs score higher.

Adoption confidence100

Modeled — how confidently teams are adopting this repo. Stargazers

Maintenance quality87

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

Risk score18

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

Stays active (30d)94%

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

Stays active (90d)92%

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

Release rhythm (180d)100

Regularity of releases over the last 180 days. Releases

Maintainer bus risk (90d)10%

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.

About Storybook

Storybook is a frontend workshop for building UI components and pages in isolation. It is widely used in JavaScript-driven interface development because it gives teams a dedicated environment for iterating on components outside the full application shell. That makes it useful for design systems, shared component libraries, documentation, and UI-focused testing workflows. Teams evaluating frontend tooling often choose Storybook when they want clearer component development loops, easier collaboration between design and engineering, and more reusable interface documentation.

Join the conversation

Reviews · Questions · Posts

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

Share your experience

Write or update your review

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

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 storybookjs/storybook. Each question links through to the full answer page.

Q&A No threads yet

Be the first to ask how teams run storybook 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 storybook — 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 Visual Regression Testing and Storybook Visual Testing world.
No Spam. Unsubscribe easily at any time.

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