/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

yewstack/yew

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-30T15:57:45.350Z

1mo ago

yewstack/yew

Yew is a Rust/WebAssembly framework for building client-side web applications. It is active, widely adopted, and maintained as a community project with 32,503 stars, 1,455 forks, and recent commits on 2026-03-30.

Loading tags...

Stars32,503

Forks1,455

Default branchmaster

Last pushed2026-03-30T10:50:09Z

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

Maintenance:

Magnitude:

Sort:

Selected

Choose upstream unless you specifically need this fork's older custom internals or docs workflow; otherwise the fork is too stale and too divergent to be a safe adoption base.

Prefer upstream unless you explicitly need the fork's extra APIs or a legacy snapshot. This fork is stale and significantly behind, so it is better suited to experimentation or short-lived internal use than as a base for new production work.

Prefer upstream unless you specifically need this older snapshot. The fork adds no visible capability and mainly carries maintenance risk from being 162 commits behind.

Prefer upstream unless you specifically need this fork's older snapshot or documentation curation. This fork looks stale and heavily diverged, so it is better for legacy maintenance than for new Yew adoption.

Choose this fork only if you explicitly need legacy Yew behavior or a bespoke branch to maintain. For new adoption, current upstream is the safer choice.

Prefer upstream unless you specifically need this older divergent codebase. This fork looks like a stale, highly modified snapshot with meaningful internal experimentation, but it is too far behind for most new adopters.

Prefer upstream unless you specifically need this fork's older experimental behavior or want a historical base to extend; for production or active development, the fork is too stale and diverged to be a good adoption target.

Choose upstream unless you specifically need this fork's older, experimental Yew behavior. For active development, the fork is too stale and too divergent to be a practical base.

Prefer upstream unless you specifically need this fork’s customized docs/history layout or a legacy-maintenance branch. The fork looks substantially diverged and more brittle for adopters who want current Yew behavior and documentation.

Prefer upstream unless you specifically need this older snapshot; the fork adds no visible capabilities and is substantially behind on maintenance and fixes.

Fork comparison

alstn2468/yew

38/100

stale

significant_divergence

Choose upstream unless you specifically need this fork's older custom internals or docs workflow; otherwise the fork is too stale and too divergent to be a safe adoption base.

Likely purpose

To experiment with or maintain an older fork of Yew that reworks core virtual DOM / component internals and documentation structure rather than tracking upstream closely.

Best for

Teams already committed to this exact fork and willing to own the merge burden.; Developers investigating historical Yew internals or a custom rendering/SSR branch.; Not a good default for new Yew adopters who want the maintained upstream line.

Additional features

Large-scale internal rendering and component-path changes in `virtual_dom`, `dom_bundle`, and component lifecycle code, suggesting custom framework behavior or an internal refactor.
Hydration-related test changes, indicating work on server/client render reconciliation or SSR workflow validation.
Documentation and site restructuring, including versioned docs and localized content paths, suggesting a fork that prioritizes custom docs delivery or translation workflows.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

It is far behind upstream activity and likely misses years of upstream bug fixes, dependency updates, and framework improvements.
Recent upstream maintenance such as docs link updates, dependency bumps, and runtime/tooling fixes are not reflected here.
Users will not get the current upstream cadence for examples, website, API-docs, or CI updates without significant merge work.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Very large divergence gives flexibility for bespoke framework behavior.
Could suit teams maintaining an older Yew-based product that depends on this fork's historical internals.
Docs and localization changes suggest it may have been adapted for a custom documentation workflow.

Risks

High merge cost with upstream because the fork is both old and substantially behind.
The scale of deletions and renames suggests major API or internal incompatibilities.
Low maintenance activity makes it a risky base for new projects or long-term adoption.