VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

css-what: vulnerability history, versions and safety

css-what is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Jun 2021 to Oct 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all css-what vulnerabilities

Vulert verdict on css-what 8.0.0 i

Updated on 23 Oct 2026

Good news: 8.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 8.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 01 Oct 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 3,301 packages i
  • Stars 250 i
  • OpenSSF scorecard 5/10 i
  • Last release 7 months ago i
  • Licence BSD-2-Clause i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for css-what, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
8.0.0 17 Mar 2026 none BSD-2-Clause — Details →
7.0.0 29 Jun 2025 none BSD-2-Clause — Details →
6.2.2 28 Jun 2025 none BSD-2-Clause — Details →
6.2.1 28 Jun 2025 none BSD-2-Clause — Details →
6.2.0 28 Jun 2025 none BSD-2-Clause — Details →
6.1.0 31 Mar 2022 none BSD-2-Clause — Details →
6.0.1 27 Dec 2021 none BSD-2-Clause — Details →
6.0.0 26 Dec 2021 none BSD-2-Clause — Details →
5.1.0 10 Oct 2021 none BSD-2-Clause — Details →
5.0.1 28 May 2021 none BSD-2-Clause — Details →
5.0.0 09 Mar 2021 H1 BSD-2-Clause Yes Details →
4.0.0 13 Oct 2020 H1 BSD-2-Clause Yes Details →
3.4.2 09 Oct 2020 none BSD-2-Clause — Details →
3.4.1 01 Oct 2020 none BSD-2-Clause — Details →
3.4.0 01 Oct 2020 none BSD-2-Clause — Details →
3.3.0 31 May 2020 none BSD-2-Clause — Details →
3.2.1 09 Nov 2019 none BSD-2-Clause — Details →
3.2.0 02 Aug 2019 none BSD-2-Clause — Details →
3.1.0 23 Jul 2019 none BSD-2-Clause — Details →
3.0.2 13 Jul 2019 none BSD-2-Clause — Details →
3.0.1 13 Jul 2019 none BSD-2-Clause — Details →
3.0.0 13 Jul 2019 none BSD-2-Clause — Details →
2.1.3 14 Feb 2019 none BSD-2-Clause — Details →
2.1.2 21 Oct 2018 H1 BSD-2-Clause Yes Details →
2.1.0 22 Nov 2015 H1 non-standard Yes Details →
2.0.2 12 Mar 2015 H1 non-standard Yes Details →
2.0.1 05 Mar 2015 H1 non-standard Yes Details →
2.0.0 01 Mar 2015 H1 non-standard Yes Details →
1.0.0 03 Feb 2015 H1 non-standard Yes Details →

All 29 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for css-what

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-33587: Denial of Service in css-what 7.5 high 5.0.1 07 Jun 2021
CVE-2022-21222: Vulnerability in css-what package allows Regular Expression Denial of Service (ReDoS) 7.5 high 2.1.3 01 Oct 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About css-what

Is css-what safe to use?

Vulert records 2 vulnerabilities for css-what in npm: 0 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is css-what's Vulert package health score?

Vulert scores css-what 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of css-what affected?

No. 8.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of css-what should I use?

8.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does css-what have?

2 vulnerabilities are recorded for css-what in the npm ecosystem: 0 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new css-what vulnerabilities disclosed?

0 vulnerabilities were recorded for css-what in the last 12 months, and the oldest entry in this database dates to 07 Jun 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of css-what are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor css-what for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the css-what version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.