tailwind-merge 2.2.0

Merge Tailwind CSS classes without style conflicts

tailwind-merge@2.2.0 was published on 2023-12-21. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All tailwind-merge versions · Permanent reference to 2.2.0 · View npm registry JSON · Latest release

Package specifications

Version2.2.0
License declarationMIT
Published2023-12-21T20:06:04.307Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size679.45 KiB
Published file count27
Package typeNot declared
ES module entryNot declared
Default entry./dist/bundle-cjs.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies1
Repository stars5701
Repository forks112

Install tailwind-merge 2.2.0

npm install tailwind-merge@2.2.0
pnpm add tailwind-merge@2.2.0
yarn add tailwind-merge@2.2.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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-Review1/10 — Found 2/12 approved changesets -- score normalized to 1
Maintained10/10 — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies6/10 — dependency not pinned by hash detected -- score normalized to 6
Token-Permissions7/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Packaging10/10 — packaging workflow detected
SAST7/10 — SAST tool detected but not run on all commits

Evidence and freshness