# rrousselGit/riverpod

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

Repository: https://github.com/rrousselGit/riverpod
Canonical: https://ross.abutalabs.com/products/riverpod
Homepage: https://riverpod.dev
Language: Dart
License: MIT
License Family: permissive
Topics: provider, flutter, state-management, dart, service-locator, inheritedwidget, riverpod, hacktoberfest
Last push: 2026-08-24T21:54:31+00:00

## Health v2 (maintenance only)
Score: 77/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 35, longevity 100
- inputs: {"age_days": 2330, "days_push": 9, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 7372, forks 1110 (observed 2026-08-28T04:09:58.567146+00:00)

## What it is
Riverpod is a reactive caching and data-binding framework for Dart and Flutter that provides compile-safe state management. It lets developers define providers as memoized functions that cache results, handle loading/error states automatically, and work in plain Dart as well as Flutter.

## Use cases
- manage app state in flutter apps
- cache network request results in dart
- handle loading and error states for async data
- share state across widgets without prop drilling
- implement pull-to-refresh or search-as-you-type patterns
- write testable business logic separate from ui
- cache api responses keyed by parameters like user id
- use state management in pure dart servers or clis

## When to choose
- building flutter or dart applications needing scalable shared state
- you want compile-time safety and lint rules for state management
- you need automatic caching, invalidation, and disposal of async data
- you want logic separated from ui and easily testable

## When to avoid
- managing purely ephemeral widget-local state like form inputs or animations
- working outside the dart/flutter ecosystem
- you prefer a minimal solution without learning provider scoping concepts

## Facets
- artifact type: framework
- maturity: active
- function: state-management, caching, middleware
- domain: mobile-development, frontend, web-development, cross-platform
- platform: cross-platform
- tags: flutter, dart, reactive-programming, service-locator, inheritedwidget, code-generation, async, dependency-injection, mobile, web-server

## Member repositories
- rrousselGit/riverpod (main) score 77

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:58.567146+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:38:23.538074+00:00, confidence not recorded.
  - readme: https://github.com/rrousselGit/riverpod (fetched 2026-08-28T04:09:58.567146+00:00, sha e0689bd91f46)
  - homepage: https://riverpod.dev (fetched 2026-08-29T08:33:46.014463+00:00, sha 21b1c98d9a2a)
  - site_page: https://riverpod.dev/docs/introduction/getting_started (fetched 2026-08-29T08:33:46.035153+00:00, sha b1286b362888)
  - site_page: https://riverpod.dev/docs/concepts2/providers (fetched 2026-08-29T08:33:46.037758+00:00, sha 03ba200d8ec0)
  - site_page: https://riverpod.dev/docs/concepts2/family (fetched 2026-08-29T08:33:46.039920+00:00, sha 5b4d10c67648)
  - site_page: https://riverpod.dev/docs/whats_new (fetched 2026-08-29T08:33:46.042144+00:00, sha 4184ad4b6ad3)
  - site_page: https://riverpod.dev/docs/root/FAQ (fetched 2026-08-29T08:33:46.055018+00:00, sha 0614fcc45ea9)
  - site_page: https://riverpod.dev/docs/root/do_dont (fetched 2026-08-29T08:33:46.081892+00:00, sha abf1dfd0245c)
- Data as of 2026-08-30T08:39:29.467469+00:00.