tailwindlabs/tailwindcss

Choose this fork only if you explicitly want its older, divergent behavior set and are prepared to maintain it yourself. If you want current Tailwind releases, bug fixes, and compatibility work, upstream is the better choice.

Prefer upstream unless you specifically need a clean, stable snapshot to customize yourself. This fork adds no observable features and is already behind recent upstream work.

Prefer upstream unless you specifically need the fork's early Oxide import and content-detection behavior. This fork looks like a frozen experiment, not a maintained alternative, so it is best for legacy reproduction or selective backporting rather than active adoption.

Prefer this fork only if its extra template and extraction support matches your stack and you can absorb long-term maintenance. If you mainly want current Tailwind behavior and upstream compatibility, the official repository is the safer choice.

Prefer upstream for any active project. Choose this fork only if you specifically need the older 2017-era Tailwind behavior or a historical base to build on. The fork is stale and materially behind upstream.

Choose this fork only if you want a clean upstream mirror; otherwise upstream is the better default because it is newer and this fork adds no observable capability.

Choose upstream unless you specifically want a minimal personal mirror; this fork shows no added capabilities and is already behind by 31 commits.

Prefer upstream unless you specifically need this older experimental branch or are extending it for internal framework work. This fork is not a good default for new adopters because it is materially behind and likely to be costly to maintain.

Choose this fork only if you need its experimental, trimmed-down behavior and are prepared to live without upstream compatibility features. For general Tailwind adoption, upstream is the safer and far more current choice.