macOS
brew install tailwindcsslocal Homebrew formula metadata
brew
Utility-first CSS framework. Version 4.3.2 via Homebrew; verified 2026-07-01.
install
brew install tailwindcsslocal Homebrew formula metadata
nix profile install nixpkgs#tailwindcssnixpkgs package indexes · pkgs/by-name/ta/tailwindcss/package.nix · source: api.github.com
scoop install main/tailwindcssScoop official bucket manifest trees · bucket/tailwindcss.json · source: api.github.com
overview
Utility-first CSS framework
history
Tailwind CSS is a utility-first CSS framework and command-line build tool for generating CSS from utility classes found in project source files. Tailwind Labs describes it as fast, flexible, reliable, and zero-runtime, with official docs centered on Vite, PostCSS, the Tailwind CLI, framework guides, and Play CDN usage.
Tailwind CSS grew out of the utility-first CSS movement and reached a stable 1.0 milestone before the 2.0 release. The official Tailwind CSS v2.0 announcement says v1.0 had been released almost exactly 18 months earlier and describes v2.0 as the framework's first major update, adding a new color palette, dark mode support, wider breakpoints, form styles, and other utility expansions.
Tailwind CSS v2.1 brought the Just-in-Time engine into core as an opt-in feature after the separate JIT preview, changing Tailwind from a mostly ahead-of-time utility generator into a faster on-demand compiler. Tailwind CSS v2.2 followed with a rewritten high-performance CLI, making the command-line package itself a first-class workflow.
Tailwind CSS v4.0 was announced as a ground-up rewrite optimized for performance and modern CSS. The v4 docs and blog emphasize CSS-first configuration with `@theme`, automatic content detection, built-in import handling, and first-party integration through `@tailwindcss/cli` and `@tailwindcss/vite`.
Tailwind's adoption is visible in its packaging surface: npm is primary, but Homebrew, Nix, and Scoop package the CLI for users who want a system-level executable. The official README points users to tailwindcss.com for documentation and to GitHub Discussions for community support, while the docs provide framework-specific installation paths.
The framework also developed an ecosystem around editor support, Headless UI, Heroicons, Tailwind Plus, and Tailwind Play. For package-manager users, that ecosystem matters because Tailwind is often installed both as a project dependency and as an editor or CLI tool.
Official CLI documentation installs `tailwindcss` and `@tailwindcss/cli`, imports `@import "tailwindcss";` in a CSS file, and runs `npx @tailwindcss/cli -i ./src/input.css -o ./src/output.css --watch`. Tailwind then scans templates for class names and generates the corresponding static CSS.
Current v4 customization is primarily CSS-driven through theme variables and directives. Legacy JavaScript configuration can still be loaded with `@config`, but the docs mark that path as compatibility for Tailwind CSS v3.x projects and note unsupported v4 options.
Tailwind CSS is package-nerd significant because it sits at the intersection of frontend build tooling, package-manager workflows, and editor tooling. It is commonly pulled through npm in projects but also packaged as a standalone CLI for Homebrew and other managers, making it a frequent test case for how JavaScript build tools are wrapped for system package ecosystems.
Its evolution from configuration-heavy JavaScript files toward CSS-first configuration and standalone CLI packages also tracks a broader packaging concern: reducing required toolchain assumptions while keeping fast incremental builds and framework integration.
security posture
No matching local secret-handling manifest was found for tailwindcss. Nucleus package metadata is still published here so future coverage has a stable package URL.
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
tailwindcss | cli | global executable |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:tailwindcss |
|---|---|
| Version | 4.3.2 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/tailwindcss |
| Homepage | https://tailwindcss.com |
| Repository | https://github.com/tailwindlabs/tailwindcss |
| Upstream docs | https://tailwindcss.com/docs |
| License | MIT |
| Source archive | https://registry.npmjs.org/@tailwindcss/cli/-/cli-4.3.2.tgz |
| Last updated | 2026-07-01T04:28:24Z |
| Pulse | updated |
| Dependencies | node |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | tailwindcss |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
tailwindcss
nix profile install nixpkgs#tailwindcssmain/tailwindcss
scoop install main/tailwindcsssource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.