Vulnerability Database · npm · Package report

es5-ext: vulnerability history, versions and safety

es5-ext is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 62 releases, first recorded in Feb 2024. 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 L2
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.

Vulert verdict on es5-ext 0.10.64 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release 0.10.64 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 26 Feb 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 113,448 packages i
  • Stars 179 i
  • OpenSSF scorecard 2/10 i
  • Last release 31 months ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 es5-ext, 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
0.10.64 27 Feb 2024 none ISC — Details →
0.10.63 23 Feb 2024 none ISC — Details →
0.10.62 02 Aug 2022 L2 ISC Yes Details →
0.10.61 20 Apr 2022 L2 ISC Yes Details →
0.10.60 07 Apr 2022 L2 ISC Yes Details →
0.10.59 17 Mar 2022 L2 ISC Yes Details →
0.10.58 11 Mar 2022 L2 ISC Yes Details →
0.10.57 08 Mar 2022 L2 ISC Yes Details →
0.10.56 07 Mar 2022 L2 ISC Yes Details →
0.10.55 07 Mar 2022 L2 ISC Yes Details →
0.10.54 07 Mar 2022 L2 ISC Yes Details →
0.10.53 21 Nov 2019 L2 ISC Yes Details →
0.10.52 29 Oct 2019 L2 ISC Yes Details →
0.10.51 30 Aug 2019 L2 ISC Yes Details →
0.10.50 30 Apr 2019 L2 ISC Yes Details →
0.10.49 11 Mar 2019 L2 ISC Yes Details →
0.10.48 22 Feb 2019 L2 ISC Yes Details →
0.10.47 16 Jan 2019 L2 ISC Yes Details →
0.10.46 13 Aug 2018 L2 ISC Yes Details →
0.10.45 01 Jun 2018 L2 ISC Yes Details →
0.10.44 30 May 2018 L2 ISC Yes Details →
0.10.43 28 May 2018 L2 ISC Yes Details →
0.10.42 28 Mar 2018 L2 ISC Yes Details →
0.10.41 16 Mar 2018 L2 ISC Yes Details →
0.10.40 09 Mar 2018 L2 ISC Yes Details →
0.10.39 16 Feb 2018 L2 MIT Yes Details →
0.10.38 16 Jan 2018 L2 MIT Yes Details →
0.10.37 23 Nov 2017 L2 MIT Yes Details →
0.10.36 23 Nov 2017 L2 MIT Yes Details →
0.10.35 13 Oct 2017 L2 MIT Yes Details →
0.10.34 13 Oct 2017 L2 MIT Yes Details →
0.10.33 13 Oct 2017 L2 MIT Yes Details →
0.10.32 13 Oct 2017 L2 MIT Yes Details →
0.10.31 09 Oct 2017 L2 MIT Yes Details →
0.10.30 25 Aug 2017 L2 MIT Yes Details →
0.10.29 18 Aug 2017 L2 MIT Yes Details →
0.10.28 18 Aug 2017 L2 MIT Yes Details →
0.10.27 11 Aug 2017 L2 MIT Yes Details →
0.10.26 02 Aug 2017 L2 MIT Yes Details →
0.10.25 02 Aug 2017 L2 MIT Yes Details →
0.10.24 10 Jul 2017 L2 MIT Yes Details →
0.10.23 05 Jun 2017 L2 MIT Yes Details →
0.10.22 31 May 2017 L2 MIT Yes Details →
0.10.21 22 May 2017 L2 MIT Yes Details →
0.10.20 17 May 2017 L2 MIT Yes Details →
0.10.19 17 May 2017 L2 MIT Yes Details →
0.10.18 15 May 2017 L2 MIT Yes Details →
0.10.17 15 May 2017 L2 MIT Yes Details →
0.10.16 09 May 2017 L2 MIT Yes Details →
0.10.15 20 Mar 2017 L2 MIT Yes Details →
0.10.14 15 Mar 2017 L2 MIT Yes Details →
0.10.13 13 Mar 2017 L2 MIT Yes Details →
0.10.12 01 Jul 2016 L2 MIT Yes Details →
0.10.11 18 Dec 2015 L2 MIT Yes Details →
0.10.10 11 Dec 2015 L2 MIT Yes Details →
0.10.9 01 Dec 2015 L2 MIT Yes Details →
0.10.8 02 Oct 2015 L2 MIT Yes Details →
0.10.7 22 Apr 2015 L2 MIT Yes Details →
0.10.6 02 Feb 2015 L2 MIT Yes Details →
0.10.5 20 Jan 2015 L2 MIT Yes Details →
0.10.4 30 Apr 2014 L2 ISC Yes Details →
0.10.3 29 Apr 2014 L2 ISC Yes Details →
0.10.2 24 Apr 2014 L2 ISC Yes Details →
0.10.1 13 Apr 2014 L2 ISC Yes Details →
0.9.2 11 Mar 2013 none ISC — Details →
0.9.1 17 Sep 2012 none ISC — Details →
0.9.0 13 Sep 2012 none ISC — Details →
0.8.2 22 Jun 2012 none ISC — Details →
0.8.1 13 Jun 2012 none ISC — Details →
0.8.0 28 May 2012 none ISC — Details →
0.7.1 02 May 2012 none ISC — Details →
0.7.0 27 Dec 2011 none ISC — Details →
0.6.3 12 Dec 2011 none ISC — Details →
0.6.2 12 Aug 2011 none ISC — Details →
0.6.1 08 Aug 2011 none ISC — Details →
0.6.0 07 Aug 2011 none ISC — Details →
0.5.1 11 Jul 2011 none ISC — Details →
0.5.0 07 Jul 2011 none ISC — Details →
0.4.0 05 Jul 2011 none ISC — Details →
0.3.0 24 Jun 2011 none ISC — Details →
0.2.1 28 May 2011 none ISC — Details →
0.2.0 28 May 2011 none ISC — Details →
0.1.0 24 May 2011 none ISC — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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 es5-ext

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 es5-ext

Is es5-ext safe to use?

Vulert records 2 vulnerabilities for es5-ext in npm: 0 critical, 0 high, 0 medium and 2 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 es5-ext's Vulert package health score?

Vulert scores es5-ext 69/100, which reads as usable, but worth attention. 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 es5-ext affected?

No. 0.10.64, 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 es5-ext should I use?

0.10.64 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 es5-ext have?

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

How often are new es5-ext vulnerabilities disclosed?

0 vulnerabilities were recorded for es5-ext in the last 12 months, and the oldest entry in this database dates to 26 Feb 2024. 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 es5-ext 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 es5-ext for upcoming vulnerabilities?

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