binarywang/WxJava

Prefer upstream unless you specifically need this fork’s old code snapshot for an existing deployment. For new work, the fork is too stale and too far behind to be a safe default.

Prefer upstream unless you specifically need this fork’s older baseline or one of its narrow backported fixes. For most adopters, the fork is too stale and too diverged to be a safe default.

Prefer upstream unless you must preserve this fork's exact older behavior or have already built local changes on top of it. For new adopters, the fork is too stale and too divergent to be the default choice.

Prefer upstream unless you must preserve a legacy integration that depends on this old fork’s API shape or a specific historical patch. For new work, the fork is too stale and too divergent to be a safe default.

Prefer upstream unless you specifically need this old customized snapshot and are prepared to maintain it yourself. For new work, the fork is too stale and too far from upstream to be a safe default.

Prefer upstream unless you are locked to this fork already. This fork is best treated as a legacy snapshot with substantial feature and maintenance lag, not a modern starting point.

Choose the upstream project unless you specifically want a near-empty fork as a snapshot. This fork adds no visible capabilities and is materially behind upstream, so it is a poor choice for adopters who want active maintenance or the latest WeChat API coverage.

Prefer upstream unless you are already committed to this fork’s historical behavior. This fork looks like a frozen, highly divergent snapshot with significant feature loss risk and little evidence of ongoing maintenance.

Prefer upstream unless you are tied to this fork’s exact legacy behavior. This fork looks like a stale, highly customized snapshot, not a healthy long-term base for new work.