/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

apache/superset

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-30T11:42:02.193Z

3mo ago

apache/superset

Apache Superset is a large, actively maintained Apache-licensed data visualization and business intelligence platform. It is a high-interest fork target because it has very high adoption signals: 71,675 stars, 16,921 forks, and recent commits as of 2026-03-30.

Loading tags...

Stars71,675

Forks16,921

Default branchmaster

Last pushed2026-03-30T10:39:17Z

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

Prefer this fork only if you specifically need its Chinese-localized legacy snapshot. For most adopters, upstream Superset is the better choice because this fork is substantially outdated and likely missing many modern capabilities and fixes.

Choose this fork only if you need its legacy UX changes or must stay close to an old Caravel-era codebase. For new deployments, upstream Superset is the safer choice because this fork is extremely stale and far behind current development.

Prefer this fork only if you specifically need its older incubator-era behavior or its local customizations. For most adopters, current upstream Superset is the better choice because this fork is stale and materially behind.

Choose this fork only if you need its legacy customizations and are prepared to maintain a very old codebase yourself. For new adopters, upstream Apache Superset is the safer choice because this fork is stale, far behind, and likely missing most modern capabilities.

Choose this fork if you want a customized, actively maintained Superset derivative with a few tangible workflow improvements and you are comfortable owning divergence. Choose upstream if you need the most current features, docs, translations, and the lowest integration risk.

Prefer this fork only if you specifically need its older customized baseline and are prepared to maintain it yourself. For most adopters, upstream Superset is the safer choice because this fork is far behind, heavily diverged, and likely missing many recent fixes and features.

Prefer this fork only if embedded rendering or its downstream tweaks solve a real deployment need. If you want the broadest feature coverage, freshest fixes, and lowest maintenance burden, upstream Superset is the safer choice.

Choose this fork only if its custom workflow changes are specifically what you need. If you want current Superset features, active maintenance, or broad translation/docs coverage, upstream is the safer choice.

Prefer this fork only if you need legacy Caravel behavior or are deliberately freezing on an old exploratory BI codebase. For new adopters, upstream Apache Superset is the clearly better choice because this fork is stale and far behind.

Choose this fork only if you need to preserve legacy Caravel-era behavior or specific old datasource quirks. For new adoption, current Apache Superset is the safer and far more capable choice.

Fork comparison

user0650/incubator-superset

38/100

stale

significant_divergence

Prefer this fork only if you specifically need its Chinese-localized legacy snapshot. For most adopters, upstream Superset is the better choice because this fork is substantially outdated and likely missing many modern capabilities and fixes.

Likely purpose

Provide a Chinese-localized Superset distribution on an older branch for users who wanted translated UI and a stable legacy snapshot instead of staying on upstream.

Best for

Chinese-speaking analytics teams that specifically need a translated legacy Superset build.; Organizations maintaining an old Superset deployment and unwilling to absorb upstream churn.; Teams prioritizing short-term compatibility over current upstream features and security posture.

Additional features

Extensive Chinese localization/translation work across the UI and documentation.
Legacy snapshot behavior that may suit teams needing an older Superset version with historical dashboard and explore behavior.
Large visual/data asset additions such as country GeoJSON coverage, suggesting packaged map/chart support in the forked snapshot.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

It is far behind upstream and likely misses years of Superset development, fixes, and security updates.
It likely lacks newer upstream products and workflows such as the embedded SDK, extension tooling, websocket-related features, and recent SQL Lab / Explore improvements.
The fork appears to have frozen around older dashboard-era code, so newer dashboard and charting behavior from upstream is not available or is harder to use.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Best fit for Chinese-speaking teams that need a translated Superset experience.
May be easier to adopt as a legacy stable snapshot if compatibility with older deployments matters more than upstream freshness.
Large amount of localization work suggests a more complete non-English UX than upstream at that point in time.

Risks

Severely stale relative to upstream, with a 2018 last push date and a large behind count.
High maintenance risk because it is unlikely to receive modern bug fixes, dependency updates, or security patches.
Large divergence makes future rebases or migrations costly.

apache/superset · Discofork