Discofork
Repository brief

Semantic-Org/Semantic-UI

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:29:00.786Z
3mo ago

Semantic-Org/Semantic-UI

Semantic UI is a mature UI component framework focused on theming and concise HTML/JavaScript. The repo is active but low-churn: it has 51,120 stars, 4,891 forks, is not archived, and the latest recorded push was 2024-11-27. The current release in the repo metadata is 2.5.0, with Node 18 and Gulp 4 compatibility noted in the README.

GitHub
Loading tags...
Stars51,120
Forks4,891
Default branchmaster
Last pushed2024-11-27T21:01:48Z
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

Choose this fork only if Portuguese localization is the main requirement and you can tolerate a very old codebase. For anything needing current Semantic UI behavior, this is a poor adoption target versus upstream.

Prefer this fork only if you need an untouched historical snapshot. For any active project, upstream is the better choice because this fork adds no visible value and is far behind current Semantic UI.

Prefer upstream unless you specifically need this exact snapshot; this fork adds no visible value and is slightly behind.

Choose this fork only if the section-limited build behavior is the main requirement and you are comfortable inheriting an old, largely unmaintained Semantic UI base. For general adoption, upstream is the safer choice.

Prefer upstream Semantic UI unless you specifically need a frozen legacy snapshot. This fork adds no visible features and is far behind on maintenance, so it is a poor choice for new adopters.

Choose this fork only if you need the specific 2015-era Semantic UI snapshot and can tolerate heavy technical debt. For new work, or for teams that want active upstream compatibility and updates, the mainline repository is the safer choice.

Prefer this fork only if Stylus is a hard requirement and you are willing to own the maintenance burden. For most new work, upstream Semantic UI is the safer choice because this fork is deeply stale and materially behind.

Prefer upstream unless you specifically need the fork’s legacy/backported behavior. This fork is materially behind and looks best for conservative, compatibility-driven adopters rather than teams wanting an actively maintained base.

Prefer upstream unless you specifically need this frozen snapshot; the fork adds no features and is materially behind.

Prefer upstream unless you specifically need an old, unmodified snapshot. This fork has no visible feature gains, no unique commits, and is materially stale.