sarink/material-ui-with-sass
stale
significant_divergence
Selected Choose this fork only if you need its legacy Sass-centric customizations and are willing to stay on an old codebase. For any new or actively maintained product, upstream is the safer and more capable base.
iKowalchuk/material-ui
stale
significant_divergence
Prefer this fork only if you specifically want its older experimental MUI/Pigment CSS direction and custom demo tooling. For most adopters, upstream is the better choice because this fork is stale and materially behind current maintenance.
shinbatsu/material-ui
stale
significant_divergence
Choose this fork only if you need its custom theming/docs behavior and can afford ongoing merge work. If you want the safest, most up-to-date MUI baseline, upstream is the better default.
JinSSJ3/material-ui
stale
significant_divergence
Choose this fork only if you want an older, highly customized Material-UI snapshot and value the Framer/benchmark artifacts more than ongoing upstream compatibility. For most adopters building a modern React product UI, upstream is the safer choice.
oliviertassinari/material-ui
stale
significant_divergence
Choose this fork if you want a customized, older MUI base with extra docs/theme/demo workflows and can absorb significant merge debt. Avoid it if you want to stay close to current upstream Material UI or depend on fast upstream updates.
jayachandragoteti/material-ui
stale
significant_divergence
Choose this fork only if you explicitly need a frozen legacy Material-UI base or its custom design/benchmark assets. For most adopters, upstream is the better choice because it is actively maintained and far ahead in fixes, tooling, and ecosystem support.
techwithtim/material-ui
stale
significant_divergence
Choose this fork only if you need the older, customized Material-UI snapshot and can own the maintenance burden. For new work, the stale activity and major divergence make upstream a much better starting point.
shimonmagal/material-ui
stale
significant_divergence
Choose this fork only if you specifically need its older baseline or Framer-oriented customization path. For most adopters, upstream MUI is the better choice because it is current, actively maintained, and far less risky to adopt.
node-on-fhir/material-fhir-ui-deprecated
stale
significant_divergence
Choose this fork only if you need its healthcare-specific behavior and can accept a frozen, deprecated codebase. For most adopters, upstream Material UI is the safer and more maintainable baseline.
renbaoshuo/material-ui
stale
significant_divergence
Choose this fork only if you specifically need its early Joy/customization work or want to continue from an old MUI snapshot. For most adopters, upstream is the better default because it is far more active and much more current.