ionic-team/ionic-framework

Prefer the upstream project unless you specifically need a legacy 2019 Ionic snapshot. This fork looks stale and substantially behind, so it is a poor choice for new work or for staying current, but it may be useful as an archival compatibility baseline.

Prefer upstream unless you specifically need this fork’s localized historical content. For active app development, the fork is too stale and too far behind to be a safe starting point.

Choose upstream unless you specifically need this old Ionic snapshot. The fork is stale, far behind current development, and looks better as a legacy reference than as a base for new work.

Prefer upstream unless you specifically need an older Ionic snapshot or this fork's local workflow changes; for active product work, this fork is too stale and diverged to be a low-risk base.

Prefer upstream unless you specifically need a frozen 2020 Ionic baseline. This fork is best for legacy maintenance or archaeology, not for building on current Ionic.

Prefer upstream unless you specifically need this fork's older 2020 behavior or one of its small set of added UI/SSR tweaks. For most adopters, the fork is too stale and too far behind to be a good starting point.

Prefer upstream unless you are committed to legacy Ionic 2 compatibility or already depend on this fork's old custom behavior. For new work, this fork is too stale and too far behind to be a sensible base.

Choose this fork only if you need the Meteor packaging or legacy Ionic 1 behavior it preserved. For new work, the upstream project is vastly more current and better maintained; this fork is a historical, highly diverged legacy branch.

Choose this fork only if you are maintaining legacy Ionic 1/AngularJS code and want a frozen, vendored framework snapshot. If you need an actively supported cross-platform UI toolkit, the upstream Ionic Framework is the better fit.