Discofork
Repository brief

NervJS/taro

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:56:29.153Z
1mo ago

NervJS/taro

Taro is a large, active open source cross-end framework for building Mini Program, Web, App, and React Native applications with React, Vue, and Nerv. It has a strong ecosystem footprint, with 37,375 stars, 4,898 forks, and recent commits through 2026-03-30. The repo is a multi-language monorepo with both Node.js/JavaScript and Rust components.

GitHub
Loading tags...
Stars37,375
Forks4,898
Default branchmain
Last pushed2026-03-30T11:13:51Z
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

9 of 9 fork briefs
Selected

Choose this fork only if you need its older downstream behavior or React Native-specific fixes and are willing to own the maintenance gap. For new adoption, upstream is the safer default because it is much more active and materially ahead.

Choose this fork only if you specifically want an unmodified Taro baseline to maintain yourself; otherwise upstream is the better choice because this fork adds no visible capability and is materially behind on fixes.

Choose this fork only if you want its older H5/runtime customizations and are prepared to maintain a large divergence yourself. If you want the current Taro ecosystem, active fixes, and lower upgrade risk, upstream is the better choice.

Choose this fork only if its Harmony/hybrid and router/cache changes match a concrete product need. If you want an actively maintained, broadly compatible Taro baseline, upstream is the safer choice.

Choose this fork only if you specifically need an older, unchanged Taro snapshot. For most adopters, upstream is the better choice because this fork adds nothing new and is materially behind recent fixes and feature work.

Choose this fork only if you need its legacy behavior or custom changes and are prepared to live without upstream progress. For new work, upstream is the safer choice.

Prefer upstream unless you specifically need this exact frozen snapshot; this fork adds no visible capabilities and is materially behind active upstream.

Choose this fork only if its added H5/server/runner customization is specifically what you need and you are prepared to own a stale, highly divergent codebase. If you want current Taro fixes and active maintenance, upstream is the safer default.

Choose this fork only if you already depend on its custom behavior or bundled tooling. If you want current Taro features, active fixes, and lower maintenance burden, upstream is the better default.