apache/echarts

Choose this fork only if you need its legacy compatibility behavior or are maintaining an existing deployment already tied to it. For any new project, upstream Apache ECharts is the safer choice because this fork is extremely stale and far behind current features and tooling.

Prefer upstream unless you specifically need this old fork’s legacy distribution shape or already depend on its frozen behavior. This fork is not a good choice for new projects or for anyone who wants active maintenance, modern packaging, or upstream compatibility.

Prefer upstream unless you specifically need to own this fork for internal customization. This fork currently offers no visible added capability, while carrying lag risk from being 88 commits behind.

Prefer upstream unless you specifically need a frozen snapshot or a private starting point. This fork adds no visible capabilities and is 670 commits behind, so adopters should expect to miss recent fixes and maintenance.

Choose this fork only if you need the legacy behavior and branding it preserves. For most users, upstream is the better base because this fork is extremely stale and materially diverged.

Choose this fork only if you need a legacy, frozen ECharts variant with a few enterprise/demo tweaks. If you want an actively maintained charting library or modern ecosystem support, upstream is the better fit.

Choose this fork if your priority is a local, browser-based ECharts playground for rapid demo work. Stick with upstream if you need the full maintained library, build pipeline, and broader extension ecosystem.

Prefer upstream Apache ECharts for almost any production use. Choose this fork only if you specifically need its custom test workflow setup or must stay on this older branch for a narrow internal reason.

Prefer upstream unless you specifically need this exact old snapshot. This fork adds no visible capabilities and is too stale for most production adopters.