VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

unicode: vulnerability history, versions and safety

unicode is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 33 releases, first recorded in Feb 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 unicode vulnerabilities

Vulert verdict on unicode 14.0.0 i

Updated on 22 Oct 2026

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

Package health score 57/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release 14.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 18 Feb 2019 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,066 packages i
  • Stars 12 i
  • OpenSSF scorecard 1/10 i
  • Last release 58 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 unicode, 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
14.0.0 19 Dec 2021 none MIT — Details →
13.0.0 25 Jan 2021 none MIT — Details →
12.1.0 03 Sep 2019 none MIT — Details →
11.0.1 25 Jun 2018 none MIT — Details →
11.0.0 25 Jun 2018 none MIT — Details →
10.0.0 01 Sep 2017 none MIT — Details →
9.0.1 05 Apr 2017 none MIT — Details →
9.0.0 04 Apr 2017 none MIT — Details →
0.6.1 18 Apr 2015 H1 MIT Yes Details →
0.6.0 08 Mar 2014 H1 MIT Yes Details →
0.5.3 19 Feb 2014 H1 MIT Yes Details →
0.5.2 18 Jan 2014 H1 MIT Yes Details →
0.5.1 17 Jan 2014 H1 MIT Yes Details →
0.5.0 01 Jan 2014 H1 MIT Yes Details →
0.4.9 19 Nov 2013 H1 MIT Yes Details →
0.4.8 19 Nov 2013 H1 MIT Yes Details →
0.4.7 19 Nov 2013 H1 MIT Yes Details →
0.4.6 18 Nov 2013 H1 MIT Yes Details →
0.4.5 09 Oct 2013 H1 MIT Yes Details →
0.4.4 22 Jun 2013 H1 MIT Yes Details →
0.4.3 27 Jun 2012 H1 MIT Yes Details →
0.4.2 27 Jun 2012 H1 MIT Yes Details →
0.4.1 27 Jun 2012 H1 MIT Yes Details →
0.4.0 27 Jun 2012 H1 MIT Yes Details →
0.3.1 13 Jan 2012 H1 MIT Yes Details →
0.3.0 05 Jan 2012 H1 MIT Yes Details →
0.2.1 29 Nov 2011 H1 MIT Yes Details →
0.2.0 24 Aug 2011 H1 MIT Yes Details →
0.1.4 30 May 2011 H1 MIT Yes Details →
0.1.3-7 29 May 2011 H1 MIT Yes Details →
0.1.3-6 29 May 2011 H1 MIT Yes Details →
0.1.3-5 29 May 2011 H1 MIT Yes Details →
0.1.3-4 29 May 2011 H1 MIT Yes Details →
0.1.3-3 29 May 2011 H1 MIT Yes Details →
0.1.3-2 29 May 2011 H1 MIT Yes Details →
0.1.3-1 29 May 2011 H1 MIT Yes Details →
0.1.3 25 May 2011 H1 MIT Yes Details →
0.1.2 24 May 2011 H1 MIT Yes Details →
0.1.1 22 May 2011 H1 MIT Yes Details →
0.1.0 22 May 2011 H1 MIT Yes Details →
0.0.1 18 May 2011 H1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1

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

03 Vulnerabilities

Recorded vulnerabilities for unicode

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10578: Insecure Resource Download in unicode N/A high 9.0.0 18 Feb 2019

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 unicode

Is unicode safe to use?

Vulert records 1 vulnerabilities for unicode in npm: 0 critical, 1 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 unicode's Vulert package health score?

Vulert scores unicode 57/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 unicode affected?

No. 14.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 unicode should I use?

14.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 unicode have?

1 vulnerability is recorded for unicode in the npm ecosystem: 0 critical, 1 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 unicode vulnerabilities disclosed?

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

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