refinedev/refine

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.