Is tailwind-merge-v2 safe to use?

tailwind-merge-v2 has no known vulnerabilities on the latest version (0.0.1-security). DepScope rates its health at 25/100 (unknown risk).

What is the latest version of tailwind-merge-v2?

The latest version of tailwind-merge-v2 is 0.0.1-security.

Does tailwind-merge-v2 have known vulnerabilities?

No known vulnerabilities on the latest version of tailwind-merge-v2.

Is tailwind-merge-v2 deprecated?

No, tailwind-merge-v2 is actively maintained. Latest release: 0.0.1-security.

What are alternatives to tailwind-merge-v2?

Popular alternatives to tailwind-merge-v2 in npm include: ?, semver, minimatch, debug, ansi-styles.

What license does tailwind-merge-v2 use?

License information for tailwind-merge-v2 is not declared in the registry metadata.

tailwind-merge-v2

npmv0.0.1-security

security holding package

0 versions0 deps6 weekly dl

npm/security-holder

/ 100

Health

do not use

Do not install. Package is flagged as malicious (advisory MAL-2026-315).

Health breakdown0 – 100

Vulnerabilities

none known

⚠ Malicious package

This package is flagged as malicious by the OpenSSF/OSV community feed. Do not install.

Advisory: MAL-2026-315 — Malicious code in tailwind-merge-v2 (npm)

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/tailwind-merge-v2