Is tailwindcss healthy, maintained, and safe?
Yes — tailwindcss looks healthy, actively maintained, and free of known advisories today.
The verdict
tailwindcss earns a health score of 100/100, a minimal risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Yes — tailwindcss looks healthy, actively maintained, and free of known advisories today.
Its most recent release shipped on 16 July 2026 — 11 days ago — so development is clearly active. Across 2629 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. 3 maintainers are listed on npm, so the project isn't hostage to any single contributor.
Security-wise, tailwindcss currently has a clean OSV record — no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
The signals are green today, but a clean snapshot is not a standing guarantee — packages drift. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Key facts
- Latest version
- v4.3.3
- Last release
- 16 July 2026 (11 days ago)
- Total releases
- 2629
- First release
- 6 October 2017
- Package age
- 8.8 years
- Maintainers
- 3
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is tailwindcss still maintained?
Yes — tailwindcss released as recently as 16 July 2026 (11 days ago), so it is actively maintained.
Does tailwindcss have known security vulnerabilities?
No advisories are currently recorded for tailwindcss in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is tailwindcss safe to use?
Yes — tailwindcss looks healthy, actively maintained, and free of known advisories today. OSPulse rates it 100/100 (minimal risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
tailwindcss is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.