Repo brief: tailwindlabs/tailwindcss

Generated by RepoPilot · document generated 2026-09-12 · concise human review Evidence snapshot · analyzed 2026-09-12T22:50:57.538Z · commit 90f8ff41c8e2

Verdict

Healthy — Healthy across all four use cases

• Used by 1 trusted project: shadcn-ui/ui
• Last commit 6d ago
• 18 active contributors
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Tailwind CSS is a utility-first CSS framework that generates atomic CSS classes from a configuration file, enabling rapid UI development without writing custom CSS. Core capability: scan source files for class names (like flex, p-4, text-lg) and output only the CSS rules actually used in the project. This eliminates unused styles and keeps bundle sizes small. Monorepo with packages/tailwindcss/src/ as the main engine. Core pipeline: candidate.ts extracts class names from source, canonicalize-candidates.ts normalizes them, compile.ts generates CSS. Compatibility layer under compat/ backports v3 config/plugin patterns to v4. Rust crates in crates/* handle…

Start here

Open these first:

• packages/tailwindcss/src/index.ts — Primary entry point for the Tailwind CSS compiler; orchestrates configuration loading, CSS parsing, and utility generation.
• packages/tailwindcss/src/compile.ts — Core compilation function that transforms input CSS and configuration into final stylesheet output.
• packages/tailwindcss/src/candidate.ts — Parses and interprets Tailwind utility class names into candidate objects for CSS generation.
• packages/tailwindcss/src/css-parser.ts — Tokenizes and parses CSS syntax to extract directives, selectors, and declarations.
• packages/tailwindcss/src/compat/create-compat-config.ts — Bridges v3 and v4 configuration APIs by normalizing user config into internal design-system format.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository: git clone https://github.com/tailwindlabs/tailwindcss. The workspace uses Rust and TypeScript; verify the repo manifest for exact install instructions before running build commands, as Node.js pa…

Daily commands:

Evidence insufficient for verified dev server command. Check package.json and Cargo.toml in the repository root for build/dev scripts. Likely patterns: npm install && npm run dev or cargo build for Rust componen…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 73% of recent commits
• Rust build requirement: The workspace includes Rust crates (crates/* with Cargo.toml). Building locally requires cargo and a Rust toolchain; pure Node.js installs will fail on native binding compilation.…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.