StackPrism

npm package

tailwindcss 4.1.18: no known vulnerabilities

tailwindcss 4.1.18 has no known vulnerabilities in OSV.dev. Tailwind CSS 4.1 reached end of life on Feb 18, 2026 and gets no more security fixes. Move to Tailwind CSS 4.3.

npm (opens in a new tab) describes it as “A utility-first CSS framework for rapidly building custom user interfaces.”

Known vulnerabilities
0
None in OSV.dev
Released
Dec 11, 2025
Latest is 4.3.3
Downloads last week
5.6M
4% of tailwindcss downloads
Tailwind CSS 4.1 support
End of life
Since Feb 18, 2026
Licence
MIT
OpenSSF Scorecard
6.7/10
tailwindlabs/tailwindcss (opens in a new tab)
Dependencies
None
Resolved by deps.dev

Newer releases

4.1.18 has nothing to fix today. Newer releases, for when you upgrade:

  • 4.3.3

    Newest 4.x release and the latest release. Released Jul 16, 2026.

    No known vulnerabilities

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Who is still on a vulnerable tailwindcss

0% of last week’s 137.3M tailwindcss downloads went to versions with known vulnerabilities.

From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.

Is tailwindcss the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly tailwindcss 4.1.18, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm, support dates from endoflife.date. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev and endoflife.date.