Discofork
Repository brief

vercel/swr

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T10:32:02.982Z
1mo ago

vercel/swr

vercel/swr is a mature React Hooks library for data fetching, centered on stale-while-revalidate behavior. It is actively maintained, widely used, and packaged for multiple entry points including core, infinite, immutable, subscription, mutation, and internal APIs.

GitHub
Loading tags...
Stars32,350
Forks1,325
Default branchmain
Last pushed2026-02-27T16:41:51Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Adopt this fork only if you specifically need this exact snapshot as a starting point; otherwise upstream is the better choice because this fork adds no visible capabilities and is already behind.

Choose this fork only if you specifically need Preact support and can accept an old, unmaintained codebase. For most teams, current upstream SWR is the safer default.

Choose this fork only if you need the older behavior or are maintaining a custom branch; otherwise upstream is the safer default because this fork is stale and likely missing many later fixes and refinements.

Do not adopt this fork for a new project. It is effectively an outdated snapshot of upstream SWR, with no visible added functionality and meaningful lag behind current fixes and maintenance.

Choose this fork only if you need its specific custom behavior or legacy compatibility. For new adoption, upstream vercel/swr is the safer default because this fork is materially behind and likely diverged in API surface and workflows.

Prefer upstream unless you specifically need this older branch. This fork looks stale and materially behind, so it is a poor default choice for new adopters.

Prefer this fork only if you need its specific customizations or legacy 2.0 behavior. For most adopters, upstream SWR is the better choice because this fork is stale and materially behind current fixes and package evolution.

Choose the fork only if you need this legacy branch specifically. For new work or ongoing maintenance, upstream SWR is the better default because it is much more current and feature-complete.

Prefer upstream unless you specifically need this fork's older behavior and are prepared to maintain a substantially outdated codebase. This fork is not a good default choice for new adopters.

Prefer upstream unless you explicitly need this older snapshot or its example/deploy conveniences. For most adopters, the fork is too stale and divergent to be a good base.

vercel/swr · Discofork