ColorlibHQ/AdminLTE

Choose this fork only if the iframe/tabbed portal behavior is the core requirement. For most adopters, upstream AdminLTE is the better base because this fork is heavily diverged and stale, so it trades maintainability and current platform support for niche navigation features.

Choose this fork only if Persian RTL support is the main requirement and you are comfortable owning maintenance. For most new work, upstream AdminLTE is the safer choice because this fork is heavily behind and likely missing many current fixes and tooling improvements.

Choose this fork only if you need a legacy AdminLTE stack that already fits an older Bootstrap 3 application. For new work, or for teams that value maintenance and modern tooling, the upstream project is the better default.

Choose this fork only if you specifically need a legacy Bootstrap 3-era AdminLTE base and can accept no meaningful upstream currency. For new work, upstream is the better choice; this fork is materially outdated and likely to create migration debt.

Prefer upstream unless you explicitly need a frozen legacy Bootstrap 4 baseline. This fork offers no visible enhancements, but it does carry upstream lag and likely misses newer fixes, docs, and Bootstrap 5-era behavior.

Choose this fork only if you need the older Bootstrap 3-era AdminLTE stack and its bundled legacy plugins. If you want current AdminLTE features, active maintenance, or Bootstrap 5 compatibility, upstream is the better choice.

Prefer upstream unless you specifically need this exact untouched snapshot. This fork offers no clear added capability, while it is materially behind current upstream fixes and docs.

Choose the fork only if you need a Bootstrap 3-compatible legacy dashboard with bundled older plugins. If you want an actively maintained AdminLTE base, current build tooling, or Bootstrap 5-era features, upstream is the better fit.