@tailwindcss/oxide 4.2.2

@tailwindcss/oxide@4.2.2 was published on 2026-03-18. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >= 20.

All @tailwindcss/oxide versions · Permanent reference to 4.2.2 · Latest release

Package specifications

Version4.2.2
License declarationMIT
Published2026-03-18T16:12:46.235Z
Node.js requirement>= 20
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count12
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size28.12 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies18
Repository stars98016
Repository forks7690

Install @tailwindcss/oxide 4.2.2

npm install @tailwindcss/oxide@4.2.2
pnpm add @tailwindcss/oxide@4.2.2
yarn add @tailwindcss/oxide@4.2.2

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review3/10 — Found 9/24 approved changesets -- score normalized to 3
Maintained10/10 — 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Security-Policy0/10 — security policy file not detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies10/10 — all dependencies are pinned
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Fuzzing10/10 — project is fuzzed
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness