pkg.soopen package index

brew / Rang 1582

tailwindcss mit Homebrew, Nix, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für tailwindcss in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install tailwindcss

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#tailwindcss

nixpkgs package indexes · pkgs/by-name/ta/tailwindcss/package.nix · Quelle: api.github.com

Windows

Scoopverifiziert · 92%
scoop install main/tailwindcss

Scoop official bucket manifest trees · bucket/tailwindcss.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Utility-first CSS framework

Befehle und Aliase

  • tailwindcss

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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`.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 2019: Tailwind CSS v1.0 stability milestone, referenced by the v2.0 announcement as almost exactly 18 months before v2.0.
  • 2020: Tailwind CSS v2.0 released as the first major update.
  • 2021: Tailwind CSS v2.1 merged the JIT engine into core.
  • 2021: Tailwind CSS v2.2 introduced a rewritten high-performance CLI.
  • 2025: Tailwind CSS v4.0 released as a ground-up rewrite with CSS-first configuration and modern web-platform features.

Related projects

  • Related first-party projects include Tailwind CSS IntelliSense, Headless UI, Heroicons, Tailwind Play, and Tailwind Plus. The language server and IntelliSense extension are especially relevant to CLI/package culture because they package Tailwind's class knowledge for editors.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für tailwindcss wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
tailwindcssExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version4.3.3
Manager aktualisiert2026-07-17
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:tailwindcss
Version4.3.3
PaketmanagerHomebrew
Homepagehttps://tailwindcss.com
Repositoryhttps://github.com/tailwindlabs/tailwindcss
Zuletzt aktualisiert2026-07-17T16:42:16Z
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

tailwindcss

nix profile install nixpkgs#tailwindcss
  • normalized package name match
  • Abgeglichen nach: Tailwindcss
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ta/tailwindcss/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Scoop95%

main/tailwindcss

scoop install main/tailwindcss
  • normalized package name match
  • Abgeglichen nach: Tailwindcss
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/tailwindcss.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation