apache/superset

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.