About Redux
Predictable state container for JavaScript apps with immutable updates, time travel debugging, and a vast middleware ecosystem; battle-tested alongside React.
A JS library for predictable global state management
Reliability breakdown
Component scores measured daily from GitHub activity (2026-07-15).
Activity on 20 of 90 tracked days in the last 90 and 4 of 30 in the last 30.
Merged 14 of 18 PRs opened and closed 6 of 10 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 — a steady cadence scores highest.
Last push 21 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
Open-issue load isn't tracked for this repo yet.
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Predictable state container for JavaScript apps with immutable updates, time travel debugging, and a vast middleware ecosystem; battle-tested alongside React.
Join the conversation
Share what you know about redux — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting redux.
Project Q&A
Browse implementation threads tied directly to reduxjs/redux. Each question links through to the full answer page.
Be the first to ask how teams run redux in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
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.
Share how your team uses redux — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post