Vulert records 1 vulnerabilities for y18n 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 y18n's Vulert package health score?

Vulert scores y18n 64/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 y18n affected?

No. 5.0.8, 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 y18n should I use?

5.0.8 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 y18n have?

1 vulnerability is recorded for y18n 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 y18n vulnerabilities disclosed?

0 vulnerabilities were recorded for y18n in the last 12 months, and the oldest entry in this database dates to 29 Mar 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 y18n 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 y18n for upcoming vulnerabilities?

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

Vulnerability Database · npm · Package report

y18n: vulnerability history, versions and safety

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

1 vulnerabilities recorded H1

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all y18n vulnerabilities

Vulert verdict on y18n 5.0.8 i

Updated on 22 Oct 2026

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

Package health score 64/100

Security Minor issues
Maintenance Slowing
Popularity Widely used
Community Quiet

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

Current release 5.0.8 — unaffected i
Vulnerabilities on record 1 over 1 year · 0 in the last year i
Latest disclosure 29 Mar 2021 i
Highest CVSS 7.3 i
With no published fix 0 i
Depended on by 205,442 packages i
Stars 154 i
OpenSSF scorecard 3/10 i
Last release 66 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for y18n, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
5.0.8	07 Apr 2021	none	ISC	—	Details →
4.0.3	07 Apr 2021	none	ISC	—	Details →
5.0.7	07 Apr 2021	none	ISC	—	Details →
4.0.2	07 Apr 2021	none	ISC	—	Details →
5.0.6	05 Apr 2021	none	ISC	—	Details →
3.2.2	04 Jan 2021	none	ISC	—	Details →
4.0.1	30 Nov 2020	none	ISC	—	Details →
5.0.5	25 Oct 2020	none	ISC	—	Details →
5.0.4	16 Oct 2020	none	ISC	—	Details →
5.0.3	16 Oct 2020	none	ISC	—	Details →
5.0.2	01 Oct 2020	none	ISC	—	Details →
6.0.0-alpha.0	12 Sep 2020	none	ISC	—	Details →
5.0.1	05 Sep 2020	none	ISC	—	Details →
5.0.0	05 Sep 2020	none	ISC	—	Details →
4.0.0	10 Oct 2017	none	ISC	—	Details →
3.2.1	17 Mar 2016	H1	ISC	Yes	Details →
3.2.0	21 Sep 2015	H1	ISC	Yes	Details →
3.1.0	18 Aug 2015	H1	ISC	Yes	Details →
3.0.0	29 Jul 2015	H1	ISC	Yes	Details →
2.0.0	28 Jul 2015	H1	ISC	Yes	Details →
1.1.0	28 Jul 2015	H1	ISC	Yes	Details →
1.0.0	27 Jul 2015	H1	ISC	Yes	Details →

All 22 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

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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for y18n

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2020-7774: Prototype Pollution in y18n	7.3 high	3.2.2	29 Mar 2021

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: 524171