/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

refinedev/refine

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-30T16:04:29.415Z

1mo ago

refinedev/refine

refinedev/refine is a large, active MIT-licensed React framework for internal tools, admin panels, dashboards, and B2B apps. It has high adoption signals (34,385 stars, 2,982 forks) and was updated/pushed on 2026-03-30, so forks are likely to matter if you want a maintained, actively evolving upstream rather than a dormant base.

Loading tags...

Stars34,385

Forks2,982

Default branchmain

Last pushed2026-03-30T07:25:14Z

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

9 of 9 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you want an older, heavily customized Refine base and are willing to own the maintenance burden. If you want current framework behavior, active fixes, and lower upgrade risk, upstream is the better default.

Prefer this fork only if its existing customizations are the product you want and you are prepared to maintain a large upstream gap. For most adopters building on `refine` itself, upstream is the safer choice because this fork is stale and materially behind.

Prefer this fork only if its Bun/Docker/security/inferrer snapshot fixes match your needs and you are comfortable carrying a stale, heavily diverged downstream. If you want the latest refine features and easier upgrades, upstream is the better default.

Choose upstream if you want an actively maintained refine base. Choose this fork only if you specifically want its older, customized docs/integration work and are prepared to absorb substantial merge and upgrade debt.

Choose upstream unless you specifically need a pinned snapshot; this fork adds no observable product value and is already behind active upstream work.

Choose this fork only if you need its specific downstream docs/content and generated inferencer state. If you want the best maintained base for new work, upstream refine is the safer default because this fork is substantially behind and likely costly to rebase.

Prefer upstream unless you specifically need this fork's older customizations. It is materially stale and heavily diverged, so it is a poor choice for adopters who want ongoing maintenance or current Refine capabilities.

Choose the fork only if its custom docs/blog or inferencer changes are specifically what you want. For most adopters, current upstream is the safer base because this fork is stale and materially diverged.

Prefer this fork if you need a customized refine codebase and are willing to own divergence. Prefer upstream if you want the latest maintained release line, lower merge risk, and fewer surprises in generated outputs.

Fork comparison

lc19997/refine

38/100

stale

significant_divergence

Choose this fork only if you want an older, heavily customized Refine base and are willing to own the maintenance burden. If you want current framework behavior, active fixes, and lower upgrade risk, upstream is the better default.

Likely purpose

A heavily diverged 2023-era Refine fork that looks useful as a customized snapshot for documentation-driven work, example app development, and local experimentation rather than as a current upstream base.

Best for

Teams wanting a frozen Refine snapshot to extend privately.; Developers maintaining a customized demo or documentation-oriented fork.; Users who prefer the older `next`-branch lineage over current upstream state.; People who do not need the latest upstream features or compatibility work.

Additional features

Adds an `app-crm-minimal` example.
Includes substantial documentation and blog content changes, including new blog/authors-related workflows.
Carries updated inferencer snapshot coverage for Ant Design, Mantine, and MUI.
Appears to include fork-specific cleanup and packaging work around the project toolchain.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

Lags upstream by 346 commits, so it is materially behind current Refine development.
Shows removal of `react-router-v5` support.
Shows removal of the `altogic` package/integration.
Does not track upstream activity since 2023-10-20, so newer upstream fixes and docs are missing.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 346 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Large amount of project-specific customization already applied.
Useful if you want a fixed, older baseline instead of following upstream churn.
Documentation and example content suggest it is oriented toward demoing and authoring workflows.
Some dependency and snapshot churn indicates active tailoring to the fork's own needs.

Risks

Very stale relative to upstream activity.
Large divergence makes rebasing or syncing expensive.
Default branch is `next`, which may not align with upstream expectations.
Many changed files are in docs, snapshots, and lockfiles, which can hide functional drift and maintenance debt.