rrousselgit/riverpod

A reactive caching and data-binding framework. Riverpod makes working with asynchronous code a breeze.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 16th, 2020
Open Issues & Pull Requests: 154 (-2)
GitHub issues: Enabled
Number of forks: 1,109
Total Stargazers: 7,378 (+0)
Total Subscribers: 76 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 5.4 days
90th percentile: 0.0 hours
Tracked items: 559

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 81% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 70% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 5% of issues opened in the past year have been closed. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 118
New in 7 days: 2
Closed in 7 days: 3
Avg open age: 416 days
Stale 30+ days: 108
Stale 90+ days: 87

Recent activity

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

Top labels

  • bug (285)
  • needs triage (244)
  • enhancement (176)
  • question (90)
  • documentation (82)
  • linter (16)
  • breaking (15)
  • with-repro (15)

Detailed Description

Riverpod is a reactive caching and data-binding framework for Dart that simplifies asynchronous state management in Flutter applications.

The framework addresses the complexity of handling asynchronous operations by providing built-in error and loading state management, eliminating the need for manual error catching. It supports advanced scenarios such as pull-to-refresh and separates business logic from UI code through a provider-based architecture. Developers define network requests and data dependencies using functions annotated with @riverpod, which the framework then manages reactively, automatically tracking dependencies and invalidating cached data when needed.

Riverpod suits projects where testability, scalability, and code reuse are priorities. The framework offers multiple packages tailored to different use cases: the core riverpod package for non-Flutter applications, flutter_riverpod for Flutter-specific features, and hooks_riverpod for integration with Flutter hooks. Teams should adopt it when they need to decouple business logic from UI and want automatic handling of loading and error states without boilerplate.

The project maintains active development with consistent build status checks and code coverage monitoring. Contributions are actively solicited across bug reports, documentation improvements, and feature implementations, indicating an open stance toward community involvement.