Discofork
Repository brief

twbs/bootstrap

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-30T10:28:19.805Z
3mo ago

twbs/bootstrap

twbs/bootstrap is the official Bootstrap repository: a widely used MIT-licensed front-end framework for responsive, mobile-first web development. It is active, not archived, and the default branch is `main`. The repo shows very high adoption signals, with 174,114 stars and 79,024 forks, and recent commits in March 2026 indicate ongoing maintenance. Release artifacts and package entry points are present for npm, Composer, and NuGet, alongside source, build, docs/site, and distribution assets.

GitHub
Loading tags...
Stars174,114
Forks79,024
Default branchmain
Last pushed2026-03-29T21:05:57Z
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

20 of 20 fork briefs
Selected

Prefer this fork only if you are maintaining a legacy Bootstrap 3 Sass codebase and want the historical distribution as-is. For new work or anything expecting current Bootstrap behavior, upstream is the better choice.

Choose upstream Bootstrap if you want current support, packaging, and active maintenance. Choose this fork only if you specifically want Kickstart's older, customized CSS library and are comfortable owning a stale, heavily divergent codebase.

Choose this fork only if you want an old but WordPress-oriented Bootstrap theme baseline. If you need current Bootstrap features, active maintenance, or modern packaging, upstream is the better fit.

Choose this only for legacy Bootstrap 3 Sass adoption. For anything new, the fork's age and divergence make upstream Bootstrap or a more current maintained Sass port the safer choice.

Choose this fork if RTL output is the primary requirement and you are comfortable staying on an older Bootstrap 4 branch. Choose upstream if you need active maintenance, modern Bootstrap 5 features, and a lower-risk long-term path.

Choose this fork if RTL support on Bootstrap 4 is the primary requirement and you want prebuilt assets now. Avoid it if you want current Bootstrap releases, active maintenance, or a low-drift upstream base.

Choose this fork only if you want the old Square UI presentation and can accept a frozen, heavily outdated Bootstrap branch. If you want an actively maintained framework or modern Bootstrap 5 behavior, upstream is the better default.

Choose this fork only if you are maintaining legacy Bootstrap 1.x code and want a Stylus-based, frozen variant. For new work or anything that needs current Bootstrap features and maintenance, upstream is the better choice.

Choose this fork only if you specifically need an older, RTL-customized Bootstrap variant and can accept being far behind upstream. For most users, upstream Bootstrap is the better default because it is active, current, and much better supported.

Prefer this fork only if you need its legacy customization workflow and are intentionally staying on an older Bootstrap branch. If you want current Bootstrap features, maintenance, and packaging, upstream is the better choice.

Choose this fork only if you need its AMP-specific Bootstrap 4 lineage and are willing to live with major staleness. For most adopters, upstream Bootstrap is the safer and more maintainable default.

Choose this fork only if you want its custom branding and docs-driven frontend workflow enough to accept losing upstream freshness. If you need a maintained Bootstrap foundation with predictable upgrades, upstream Bootstrap is the safer default.

Prefer this fork only if you must stay on an old Bootstrap-era codebase. For new work or active maintenance, upstream is the better choice because this fork is far behind and effectively unmaintained.

Choose this fork only if you need a legacy Django template built around old Bootstrap assets. If you want current Bootstrap features, active maintenance, or modern packaging, upstream is clearly the better fit.

Choose this fork only for legacy compatibility or archaeology. For new work or anything needing current Bootstrap capabilities, the upstream project is a much better fit.

Choose this fork only if you need its customized 5.3-era docs/site layout and are comfortable carrying an outdated Bootstrap fork. If you want current upstream fixes and lower maintenance, the official repository is the better default.

Choose this fork only if you need its legacy behavior or local docs/customizations. If you want current Bootstrap capabilities, active maintenance, or an easier upgrade path, upstream is the better default.

Prefer this fork if your priority is a customized Bootstrap docs/site workflow and you can tolerate long-term drift from upstream. Prefer upstream if you want current Bootstrap fixes, low maintenance burden, and the standard package/docs layout.

Prefer this fork only if you want the flat visual theme and are comfortable staying on an old Bootstrap branch. If you need modern Bootstrap features, active maintenance, or ecosystem compatibility, upstream is the better choice.

Choose this fork only if you want a Bootstrap 5.3 snapshot with customized docs/site structure and are willing to own long-term maintenance. If you want current Bootstrap fixes, releases, and docs, upstream is the better default.