/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

tailwindlabs/tailwindcss

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-30T12:07:41.168Z

3mo ago

tailwindlabs/tailwindcss

Tailwind CSS is a large, actively maintained utility-first CSS framework repository with a very high fork count and star count. It appears to be a multi-language monorepo centered on Rust and Node.js/JavaScript, with packaging, integrations, playgrounds, and release tooling in the tree.

Loading tags...

Stars94,219

Forks5,142

Default branchmain

Last pushed2026-03-27T15:53: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

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if its specific compiler and integration behavior is required; otherwise upstream Tailwind is the safer default because this fork is stale and materially behind.

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.

Fork comparison

iKowalchuk/tailwindcss

38/100

stale

significant_divergence

Choose this fork only if its specific compiler and integration behavior is required; otherwise upstream Tailwind is the safer default because this fork is stale and materially behind.

Likely purpose

For teams that want an older Tailwind base with customized compiler behavior and integration fixes, especially if they are maintaining a Vite-heavy or plugin-heavy setup and are willing to accept being off the upstream release cadence.

Best for

Teams already pinned to this fork and willing to own long-term maintenance.; Users with Vite/SolidStart or HTML `<style>` workflows that match the fork’s custom behavior.; Developers who need custom Tailwind parser or plugin semantics more than upstream parity.

Additional features

Transforms `<style>` blocks in HTML files for Vite workflows.
Avoids rebasing URLs that look like aliases in Vite builds.
Processes Tailwind CSS features when using `@reference`.
Prevents plugins from modifying CSS variables.
Changes parsing so invalid CSS declarations are discarded and escaped theme variables are handled correctly.
Adds custom canonicalization and utility-generation behavior, including collapsed declarations and revised grid utility output.

Missing features

Is about 200 commits behind upstream, so it likely lacks many newer fixes and release/tooling improvements from March 2026.
Appears to miss recent upstream canonicalization work for negative arbitrary values and deprecated utility handling.
Likely lacks upstream upgrade-tooling stability improvements and newer integration/test fixes.
The fork’s last push was in January 2025, so it is not keeping pace with current upstream maintenance.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

May be easier to adopt if you specifically need the fork’s Vite and `@reference` behavior.
Could be useful when you want stricter plugin isolation around CSS variables.
The fork includes substantial parser and utility canonicalization work that may reduce local edge-case bugs in older setups.

Risks

High divergence from upstream makes future merges and security/bugfix backports harder.
The repository appears stale, so adopters may inherit unresolved bugs or outdated dependencies.
Large test and lockfile churn suggest a broad behavioral rewrite rather than a narrow patch.