Discofork
Repository brief

brillout/awesome-react-components

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-30T13:04:18.875Z
3mo ago

brillout/awesome-react-components

A large, active curated index of React components and libraries, not an implementation package. It is maintained as a checklist-style resource with contribution rules that require replacing non-awesome entries when adding new ones. With 47k+ stars, 3.7k forks, and recent commits in January 2026, it looks like a high-visibility reference repo rather than a codebase you would fork for product code.

GitHub
Loading tags...
Stars47,168
Forks3,751
Default branchmaster
Last pushed2026-01-26T16:36:45Z
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

Prefer upstream unless you specifically want a quiet snapshot to customize; this fork adds nothing visible and is materially behind the maintained source.

Prefer upstream unless you explicitly need this older snapshot. This fork appears to add no user-facing capabilities and is substantially behind on curation updates, so it is mainly useful as a dormant reference copy.

Prefer upstream unless you specifically need a frozen snapshot. This fork does not add features, is far behind upstream, and offers little reason to adopt over the maintained source.

Choose upstream unless you specifically need a frozen 2021 snapshot. This fork adds no visible capability and is too stale for adoption as a living resource.

Prefer upstream unless you specifically need an old snapshot. This fork has no added capabilities, is far behind by 189 commits, and appears inactive, so it is a weaker choice for anyone relying on up-to-date React component curation.

Prefer upstream unless you specifically need an archived snapshot. This fork adds no visible capabilities and is too stale for anyone who wants current React component recommendations.

Prefer this fork only if you want a branded, standalone catalog and are comfortable owning maintenance. If you want current React component recommendations, upstream is the better choice.

Prefer upstream unless you specifically want a frozen 2016 snapshot or a custom fork to maintain yourself. For anyone choosing React libraries today, this fork is too stale to trust as a current discovery source.

Prefer upstream unless you specifically want a frozen copy; this fork has no added capabilities and is 55 commits behind an actively maintained curated index.

Prefer upstream unless you specifically want an old frozen snapshot. This fork has no visible fork-specific value and is materially stale for a curation repo that depends on freshness.