VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

uglify-es: vulnerability history, versions and safety

uglify-es 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 uglify-es vulnerabilities

Vulert verdict on uglify-es 3.3.9 i

Updated on 23 Oct 2026

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

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

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 3.3.9 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 13,904 packages i
  • Stars 10,868 i
  • OpenSSF scorecard 2/10 i
  • Last release 104 months ago i
  • Licence BSD-2-Clause i
  • Similar names uglify-js 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 uglify-es, 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
3.3.10 08 Feb 2018 none BSD-2-Clause — Details →
3.3.9 27 Jan 2018 none BSD-2-Clause — Details →
3.3.8 21 Jan 2018 none BSD-2-Clause — Details →
3.3.7 14 Jan 2018 none BSD-2-Clause — Details →
3.3.6 13 Jan 2018 none BSD-2-Clause — Details →
3.3.5 07 Jan 2018 none BSD-2-Clause — Details →
3.3.4 31 Dec 2017 none BSD-2-Clause — Details →
3.3.3 28 Dec 2017 none BSD-2-Clause — Details →
3.3.2 25 Dec 2017 none BSD-2-Clause — Details →
3.3.1 25 Dec 2017 none BSD-2-Clause — Details →
3.3.0 24 Dec 2017 none BSD-2-Clause — Details →
3.2.2 10 Dec 2017 none BSD-2-Clause — Details →
3.2.1 03 Dec 2017 none BSD-2-Clause — Details →
3.2.0 25 Nov 2017 none BSD-2-Clause — Details →
3.1.10 19 Nov 2017 none BSD-2-Clause — Details →
3.1.9 11 Nov 2017 none BSD-2-Clause — Details →
3.1.8 06 Nov 2017 none BSD-2-Clause — Details →
3.1.7 05 Nov 2017 none BSD-2-Clause — Details →
3.1.6 29 Oct 2017 none BSD-2-Clause — Details →
3.1.5 21 Oct 2017 none BSD-2-Clause — Details →
3.1.4 21 Oct 2017 none BSD-2-Clause — Details →
3.1.3 01 Oct 2017 none BSD-2-Clause — Details →
3.1.2 24 Sep 2017 none BSD-2-Clause — Details →
3.1.1 17 Sep 2017 none BSD-2-Clause — Details →
3.1.0 10 Sep 2017 none BSD-2-Clause — Details →
3.0.28 19 Aug 2017 none BSD-2-Clause — Details →
3.0.27 30 Jul 2017 none BSD-2-Clause — Details →
3.0.26 23 Jul 2017 none BSD-2-Clause — Details →
3.0.25 16 Jul 2017 none BSD-2-Clause — Details →
3.0.24 08 Jul 2017 none BSD-2-Clause — Details →
3.0.23 02 Jul 2017 none BSD-2-Clause — Details →
3.0.22 30 Jun 2017 none BSD-2-Clause — Details →
3.0.21 28 Jun 2017 none BSD-2-Clause — Details →
3.0.20 25 Jun 2017 none BSD-2-Clause — Details →
3.0.19 21 Jun 2017 none BSD-2-Clause — Details →
3.0.18 18 Jun 2017 none BSD-2-Clause — Details →
3.0.17 15 Jun 2017 none BSD-2-Clause — Details →
3.0.15 01 Jun 2017 none BSD-2-Clause — Details →
3.0.14 31 May 2017 none BSD-2-Clause — Details →
3.0.13 29 May 2017 none BSD-2-Clause — Details →
3.0.12 27 May 2017 none BSD-2-Clause — Details →
3.0.11 23 May 2017 none BSD-2-Clause — Details →
3.0.10 20 May 2017 none BSD-2-Clause — Details →
3.0.9 19 May 2017 none BSD-2-Clause — Details →
3.0.8 18 May 2017 none BSD-2-Clause — Details →
3.0.7 16 May 2017 none BSD-2-Clause — Details →
3.0.5 15 May 2017 none BSD-2-Clause — Details →
3.0.4 12 May 2017 none BSD-2-Clause — Details →
3.0.3 10 May 2017 none BSD-2-Clause — Details →
3.0.2 09 May 2017 none BSD-2-Clause — Details →

All 50 versions Vulert tracks for this package. 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 uglify-es

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 uglify-es

Is uglify-es safe to use?

Vulert has no vulnerabilities on record for uglify-es 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 uglify-es's Vulert package health score?

Vulert scores uglify-es 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of uglify-es affected?

No. 3.3.9, 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 uglify-es should I use?

3.3.9 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 uglify-es have?

0 vulnerabilities are recorded for uglify-es 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 uglify-es vulnerabilities disclosed?

0 vulnerabilities were recorded for uglify-es 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 uglify-es 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 uglify-es for upcoming vulnerabilities?

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