mantinedev/mantine

Choose this fork if you want opinionated customization and extra product-specific UI/workflow support. Avoid it if you want a stable Mantine upstream track with minimal maintenance overhead.

Prefer this fork only if its dark-theme-oriented customization and added scheduling workflow are strategically important. If you want current Mantine features, active maintenance, and low upgrade risk, upstream is the safer choice.

Choose this fork only if you specifically want a mostly-upstream Mantine base to customize locally, likely around dark theme work. For most adopters, the active upstream is the safer choice because this fork is 212 commits behind and shows no added features.

Choose this fork only if you want a customized, older Mantine branch and are comfortable owning merge debt. If you want the broadest feature set and easiest upgrade path, upstream is the safer choice.

Prefer this fork only if you need its schedule-focused and tooling-heavy customizations and are prepared to absorb substantial upstream drift. For most adopters, upstream Mantine is the safer choice because this fork is deeply divergent, behind upstream, and appears to have removed some demo/test coverage.

Prefer this fork only if its custom schedule and docs/tooling changes are the product you need. For most adopters, upstream Mantine is the safer choice because this fork is stale and substantially behind current maintenance and feature work.

Choose the fork only if its schedule/docs/tooling additions are exactly what you need and you are comfortable maintaining a heavily outdated codebase. For most adopters, upstream Mantine is the safer choice.

Prefer this fork only if you specifically need its dark-theme-centered legacy behavior and are willing to maintain a highly divergent codebase. For most adopters, upstream Mantine is the safer choice because this fork is stale and materially behind current development.

Choose this fork only if its native dark theme focus and customizations are more valuable than staying current with upstream Mantine. For most adopters, upstream is the safer default because this fork is old, highly divergent, and likely missing many newer capabilities.