legendapp/legend-state

Legend-State is a super fast and powerful state library that enables fine-grained reactivity and easy automatic persistence

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 16th, 2026
Created on July 21st, 2022
Open Issues & Pull Requests: 218 (+0)
GitHub issues: Enabled
Number of forks: 146
Total Stargazers: 4,207 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 days
Mean response time: 31.6 days
90th percentile: 79.8 days
Tracked items: 180

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 25% 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: 152
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 514 days
Stale 30+ days: 149
Stale 90+ days: 135

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)
  • done? (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Legend-State is a state management library that enables fine-grained reactivity with automatic persistence capabilities.

The library addresses the problem of managing application state efficiently while minimizing unnecessary re-renders and supporting data persistence without boilerplate. It achieves this through fine-grained reactivity, which tracks changes at a granular level so that only the specific components or computations that depend on changed values update. The automatic persistence feature allows state to be saved and restored from storage without requiring manual serialization or deserialization logic.

Developers should consider Legend-State for applications where performance is critical and where state needs to survive page reloads or application restarts. It suits projects that benefit from reactive updates without the overhead of broader re-render cycles, and applications that require straightforward persistence without complex setup. The library is particularly valuable in scenarios where fine-grained tracking prevents unnecessary computations and UI updates.

The project shows consistent development activity with regular updates and maintenance. The codebase demonstrates active refinement of core functionality and ongoing attention to performance optimization. Documentation and examples receive regular updates to reflect the library's capabilities and usage patterns.