VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@parcel/optimizer-css: vulnerability history, versions and safety

@parcel/optimizer-css is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 @parcel/optimizer-css vulnerabilities

Vulert verdict on @parcel/optimizer-css 2.16.4 i

Updated on 23 Oct 2026

Good news: 2.16.4, the version you would install today, has no known vulnerabilities.

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 2.16.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 499 packages i
  • Stars 44,006 i
  • OpenSSF scorecard 2/10 i
  • Last release 8 months ago i
  • Licence MIT 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 @parcel/optimizer-css, 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
2.16.5-canary.3498 03 Feb 2026 none MIT — Details →
2.16.4 02 Feb 2026 none MIT — Details →
2.16.4-canary.3496 07 Dec 2025 none MIT — Details →
2.16.3 06 Dec 2025 none MIT — Details →
2.16.2 06 Dec 2025 none MIT — Details →
2.16.2-canary.3489 06 Nov 2025 none MIT — Details →
2.16.1 05 Nov 2025 none MIT — Details →
2.16.1-canary.3487 24 Oct 2025 none MIT — Details →
2.16.1-canary.3486 19 Sep 2025 none MIT — Details →
2.16.0 18 Sep 2025 none MIT — Details →
2.15.5-canary.3484 31 Aug 2025 none MIT — Details →
2.15.5-canary.3483 21 Jun 2025 none MIT — Details →
2.15.4 20 Jun 2025 none MIT — Details →
2.15.3 20 Jun 2025 none MIT — Details →
2.15.3-canary.3476 08 Jun 2025 none MIT — Details →
2.15.3-canary.3473 29 May 2025 none MIT — Details →
2.15.3-canary.3472 25 May 2025 none MIT — Details →
2.15.2 25 May 2025 none MIT — Details →
2.15.2-canary.3465 21 May 2025 none MIT — Details →
2.15.2-canary.3460 19 May 2025 none MIT — Details →
2.15.2-canary.3458 17 May 2025 none MIT — Details →
2.15.1 16 May 2025 none MIT — Details →
2.15.1-canary.3456 16 May 2025 none MIT — Details →
2.15.1-canary.3455 13 May 2025 none MIT — Details →
2.15.0 12 May 2025 none MIT — Details →
2.14.5-canary.3449 11 May 2025 none MIT — Details →
2.14.5-canary.3443 11 May 2025 none MIT — Details →
2.14.5-canary.3442 30 Apr 2025 none MIT — Details →
2.14.5-canary.3441 28 Apr 2025 none MIT — Details →
2.14.5-canary.3437 31 Mar 2025 none MIT — Details →
2.14.4 29 Mar 2025 none MIT — Details →
2.14.3 29 Mar 2025 none MIT — Details →
2.14.3-canary.3428 25 Mar 2025 none MIT — Details →
2.14.2 23 Mar 2025 none MIT — Details →
2.14.2-canary.3422 21 Mar 2025 none MIT — Details →
2.14.1 19 Mar 2025 none MIT — Details →
2.14.1-canary.3417 19 Mar 2025 none MIT — Details →
2.14.0 18 Mar 2025 none MIT — Details →
2.13.4-canary.3414 18 Mar 2025 none MIT — Details →
2.13.4-canary.3412 09 Mar 2025 none MIT — Details →
2.13.4-canary.3410 06 Mar 2025 none MIT — Details →
2.13.4-canary.3404 24 Feb 2025 none MIT — Details →
2.13.4-canary.3403 21 Feb 2025 none MIT — Details →
2.13.4-canary.3402 05 Feb 2025 none MIT — Details →
2.13.4-canary.3401 03 Feb 2025 none MIT — Details →
2.13.4-canary.3400 03 Feb 2025 none MIT — Details →
2.13.4-canary.3399 21 Jan 2025 none MIT — Details →
2.13.4-canary.3398 21 Jan 2025 none MIT — Details →
2.13.4-canary.3395 12 Jan 2025 none MIT — Details →
2.13.4-canary.3393 08 Jan 2025 none MIT — Details →
2.13.4-canary.3392 06 Jan 2025 none MIT — Details →
2.13.4-canary.3391 03 Jan 2025 none MIT — Details →
2.13.4-canary.3389 31 Dec 2024 none MIT — Details →
2.13.4-canary.3388 26 Dec 2024 none MIT — Details →
2.13.4-canary.3387 24 Dec 2024 none MIT — Details →
2.13.4-canary.3386 23 Dec 2024 none MIT — Details →
2.13.4-canary.3384 17 Dec 2024 none MIT — Details →
2.13.3 16 Dec 2024 none MIT — Details →
2.13.3-dev.3418 16 Dec 2024 none MIT — Details →
2.13.3-dev.3412 10 Dec 2024 none MIT — Details →
2.13.3-dev.3404 09 Dec 2024 none MIT — Details →
2.13.3-canary.3382 28 Nov 2024 none MIT — Details →
2.13.2 25 Nov 2024 none MIT — Details →
2.13.1 25 Nov 2024 none MIT — Details →
2.13.1-canary.3372 13 Nov 2024 none MIT — Details →
2.13.0 12 Nov 2024 none MIT — Details →
2.12.1-canary.3365 11 Nov 2024 none MIT — Details →
2.12.1-canary.3364 11 Nov 2024 none MIT — Details →
2.12.1-canary.3359 10 Nov 2024 none MIT — Details →
2.12.1-canary.3358 05 Nov 2024 none MIT — Details →
2.12.1-canary.3356 15 Oct 2024 none MIT — Details →
2.12.1-canary.3355 11 Oct 2024 none MIT — Details →
2.12.1-canary.3354 01 Oct 2024 none MIT — Details →
2.12.1-canary.3353 30 Sep 2024 none MIT — Details →
2.12.1-canary.3351 29 Sep 2024 none MIT — Details →
2.12.1-canary.3350 28 Sep 2024 none MIT — Details →
2.12.1-canary.3345 28 Aug 2024 none MIT — Details →
2.12.1-canary.3344 28 Aug 2024 none MIT — Details →
2.12.1-canary.3343 22 Aug 2024 none MIT — Details →
2.12.1-canary.3342 15 Aug 2024 none MIT — Details →
2.12.1-canary.3341 13 Aug 2024 none MIT — Details →
2.12.1-canary.3340 12 Aug 2024 none MIT — Details →
2.12.1-canary.3339 12 Aug 2024 none MIT — Details →
2.12.1-canary.3338 09 Aug 2024 none MIT — Details →
2.12.1-canary.3337 08 Aug 2024 none MIT — Details →
2.12.1-canary.3336 08 Aug 2024 none MIT — Details →
2.12.1-canary.3335 06 Aug 2024 none MIT — Details →
2.12.1-dev.3335 06 Aug 2024 none MIT — Details →
2.12.1-canary.3333 05 Aug 2024 none MIT — Details →
2.12.1-canary.3332 05 Aug 2024 none MIT — Details →
2.12.1-canary.3330 02 Aug 2024 none MIT — Details →
2.12.1-canary.3329 02 Aug 2024 none MIT — Details →
2.12.1-canary.3328 02 Aug 2024 none MIT — Details →
2.12.1-canary.3327 01 Aug 2024 none MIT — Details →
2.12.1-canary.3325 31 Jul 2024 none MIT — Details →
2.12.1-canary.3323 31 Jul 2024 none MIT — Details →
2.12.1-canary.3322 30 Jul 2024 none MIT — Details →
2.12.1-canary.3320 30 Jul 2024 none MIT — Details →
2.12.1-canary.3319 29 Jul 2024 none MIT — Details →
2.12.1-canary.3318 29 Jul 2024 none MIT — Details →
2.12.1-canary.3317 26 Jul 2024 none — — Details →
2.12.1-canary.3316 26 Jul 2024 none — — Details →
2.12.1-canary.3313 24 Jul 2024 none — — Details →
2.12.1-canary.3311 23 Jul 2024 none — — Details →
2.12.1-canary.3310 19 Jul 2024 none — — Details →
2.12.1-canary.3308 17 Jul 2024 none — — Details →
2.12.1-canary.3307 17 Jul 2024 none — — Details →
2.12.1-canary.3306 17 Jul 2024 none — — Details →
2.12.1-canary.3304 15 Jul 2024 none — — Details →
2.12.1-dev.3303 15 Jul 2024 none — — Details →
2.12.1-canary.3293 11 Jul 2024 none — — Details →
2.12.1-canary.3292 11 Jul 2024 none — — Details →
2.12.1-canary.3290 26 Jun 2024 none — — Details →
2.12.1-canary.3289 26 Jun 2024 none — — Details →
2.12.1-canary.3288 25 Jun 2024 none — — Details →
2.12.1-canary.3286 25 Jun 2024 none — — Details →
2.12.1-canary.3285 25 Jun 2024 none — — Details →
2.12.1-canary.3284 24 Jun 2024 none — — Details →
2.12.1-canary.3282 21 Jun 2024 none — — Details →
2.12.1-canary.3281 21 Jun 2024 none — — Details →

The newest 120 of 543 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @parcel/optimizer-css

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 @parcel/optimizer-css

Is @parcel/optimizer-css safe to use?

Vulert has no vulnerabilities on record for @parcel/optimizer-css in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @parcel/optimizer-css's Vulert package health score?

Vulert scores @parcel/optimizer-css 79/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 @parcel/optimizer-css affected?

No. 2.16.4, 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 @parcel/optimizer-css should I use?

2.16.4 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 @parcel/optimizer-css have?

0 vulnerabilities are recorded for @parcel/optimizer-css in the npm ecosystem: 0 critical, 0 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 @parcel/optimizer-css vulnerabilities disclosed?

0 vulnerabilities were recorded for @parcel/optimizer-css in the last 12 months. 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 @parcel/optimizer-css 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 @parcel/optimizer-css for upcoming vulnerabilities?

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