VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

lazysizes: vulnerability history, versions and safety

lazysizes is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 94 releases, from Sep 2020 to Dec 2021. 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 H1 M1
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 lazysizes vulnerabilities

Vulert verdict on lazysizes 5.3.2 i

Updated on 23 Oct 2026

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

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

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

  • Current release 5.3.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 10 Dec 2021 i
  • Highest CVSS 5.4 i
  • With no published fix 0 i
  • Depended on by 308 packages i
  • Stars 17,709 i
  • OpenSSF scorecard 1/10 i
  • Last release 66 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 lazysizes, 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
5.3.2 31 Mar 2021 none MIT — Details →
5.3.1 27 Mar 2021 none MIT — Details →
5.3.0 02 Jan 2021 none MIT — Details →
5.3.0-beta1 16 Dec 2020 none MIT — Details →
5.2.2 27 May 2020 none MIT — Details →
5.2.1 25 May 2020 none MIT — Details →
5.2.1-rc2 18 May 2020 M1 MIT Yes Details →
5.2.1-rc1 17 May 2020 M1 MIT Yes Details →
5.2.0 17 Dec 2019 H1 M1 MIT Yes Details →
5.2.0-beta1 13 Nov 2019 H1 M1 MIT Yes Details →
5.1.2 05 Oct 2019 H1 M1 MIT Yes Details →
5.1.1 04 Aug 2019 H1 M1 MIT Yes Details →
5.1.0 30 May 2019 H1 M1 MIT Yes Details →
5.0.0 13 May 2019 H1 M1 MIT Yes Details →
5.0.0-rc2 08 May 2019 H1 M1 MIT Yes Details →
5.0.0-rc1 05 May 2019 H1 M1 MIT Yes Details →
5.0.0-beta2 03 May 2019 H1 M1 MIT Yes Details →
5.0.0-beta1 02 May 2019 H1 M1 MIT Yes Details →
4.1.8 22 Apr 2019 H1 M1 MIT Yes Details →
4.1.7 20 Mar 2019 H1 M1 MIT Yes Details →
4.1.6 15 Feb 2019 H1 M1 MIT Yes Details →
4.1.5 08 Dec 2018 H1 M1 MIT Yes Details →
4.1.4 05 Oct 2018 H1 M1 MIT Yes Details →
4.1.3 30 Sep 2018 H1 M1 MIT Yes Details →
4.1.2 10 Sep 2018 H1 M1 MIT Yes Details →
4.1.1 23 Aug 2018 H1 M1 MIT Yes Details →
4.1.0 06 Aug 2018 H1 M1 MIT Yes Details →
4.0.4 06 Jun 2018 H1 M1 MIT Yes Details →
4.0.3 06 Jun 2018 H1 M1 MIT Yes Details →
4.0.2 16 Mar 2018 H1 M1 MIT Yes Details →
4.0.1 27 Oct 2017 H1 M1 MIT Yes Details →
4.0.1-beta1 22 Oct 2017 H1 M1 MIT Yes Details →
4.0.0 14 Oct 2017 H1 M1 MIT Yes Details →
4.0.0-rc4 06 Oct 2017 H1 M1 MIT Yes Details →
4.0.0-rc3 15 Jun 2017 H1 M1 MIT Yes Details →
4.0.0-rc2 13 Jun 2017 H1 M1 MIT Yes Details →
4.0.0-rc1 15 May 2017 H1 M1 MIT Yes Details →
3.0.0 25 Feb 2017 H1 M1 MIT Yes Details →
3.0.0-rc4 08 Feb 2017 H1 M1 MIT Yes Details →
3.0.0-rc3 14 Jan 2017 H1 M1 MIT Yes Details →
3.0.0-rc2 28 Nov 2016 H1 M1 MIT Yes Details →
3.0.0-rc1 25 Nov 2016 H1 M1 MIT Yes Details →
2.0.7 08 Nov 2016 H1 M1 MIT Yes Details →
2.0.6 02 Nov 2016 H1 M1 MIT Yes Details →
2.0.6-rc2 29 Oct 2016 H1 M1 MIT Yes Details →
2.0.6-rc1 29 Oct 2016 H1 M1 MIT Yes Details →
2.0.5 22 Oct 2016 H1 M1 MIT Yes Details →
2.0.4 11 Oct 2016 H1 M1 MIT Yes Details →
2.0.3 11 Oct 2016 H1 M1 MIT Yes Details →
2.0.2 02 Sep 2016 H1 M1 MIT Yes Details →
2.0.2-rc1 30 Aug 2016 H1 M1 MIT Yes Details →
2.0.1 16 Aug 2016 H1 M1 MIT Yes Details →
2.0.0 29 May 2016 H1 M1 MIT Yes Details →
2.0.0-rc2 16 May 2016 H1 M1 MIT Yes Details →
2.0.0-rc1 07 May 2016 H1 M1 MIT Yes Details →
1.0.0-rc1 07 May 2016 H1 M1 MIT Yes Details →
1.0.0-alpha 03 May 2016 H1 M1 MIT Yes Details →
1.5.0 04 Apr 2016 H1 M1 MIT Yes Details →
1.5.0-rc4 27 Mar 2016 H1 M1 MIT Yes Details →
1.5.0-rc3 06 Mar 2016 H1 M1 MIT Yes Details →
1.5.0-rc1 04 Mar 2016 H1 M1 MIT Yes Details →
1.4.0 15 Jan 2016 H1 M1 MIT Yes Details →
1.4.0-rc1 04 Jan 2016 H1 M1 MIT Yes Details →
1.3.2 06 Dec 2015 H1 M1 MIT Yes Details →
1.3.1 16 Oct 2015 H1 M1 MIT Yes Details →
1.3.0 08 Oct 2015 H1 M1 MIT Yes Details →
1.2.3-rc2 06 Oct 2015 H1 M1 MIT Yes Details →
1.2.3-rc1 23 Sep 2015 H1 M1 MIT Yes Details →
1.2.2 11 Sep 2015 H1 M1 MIT Yes Details →
1.2.1 05 Sep 2015 H1 M1 MIT Yes Details →
1.2.0 28 Aug 2015 H1 M1 MIT Yes Details →
1.2.0-rc2 23 Aug 2015 H1 M1 MIT Yes Details →
1.2.0-rc1 22 Aug 2015 H1 M1 MIT Yes Details →
1.1.5 06 Aug 2015 H1 M1 MIT Yes Details →
1.1.5-rc1 04 Aug 2015 H1 M1 MIT Yes Details →
1.1.4 18 Jul 2015 H1 M1 MIT Yes Details →
1.1.4-rc1 15 Jul 2015 H1 M1 MIT Yes Details →
1.1.3 09 Jun 2015 H1 M1 MIT Yes Details →
1.1.3-RC1 03 Jun 2015 H1 M1 MIT Yes Details →
1.1.2 13 May 2015 H1 M1 MIT Yes Details →
1.1.0 19 Apr 2015 H1 M1 MIT Yes Details →
1.1.0-rc3 14 Apr 2015 H1 M1 MIT Yes Details →
1.1.0-rc2 12 Apr 2015 H1 M1 MIT Yes Details →
1.1.0-rc1 10 Apr 2015 H1 M1 MIT Yes Details →
1.0.1 13 Mar 2015 H1 M1 MIT Yes Details →
1.0.1-RC1 11 Mar 2015 H1 M1 MIT Yes Details →
1.0.0 25 Feb 2015 H1 M1 MIT Yes Details →
1.0.0-RC3 25 Feb 2015 H1 M1 MIT Yes Details →
0.9.0 02 Feb 2015 H1 M1 MIT Yes Details →
0.8.1 19 Jan 2015 H1 M1 MIT Yes Details →
0.8.0 19 Jan 2015 H1 M1 MIT Yes Details →
0.7.2 10 Jan 2015 H1 M1 MIT Yes Details →
0.7.1 01 Jan 2015 H1 M1 MIT Yes Details →
0.6.1 23 Dec 2014 H1 M1 MIT Yes Details →
0.6.0 22 Dec 2014 H1 M1 MIT Yes Details →
0.5.3 18 Dec 2014 H1 M1 MIT Yes Details →
0.5.2 17 Dec 2014 H1 M1 MIT Yes Details →
0.5.1 03 Dec 2014 H1 M1 MIT Yes Details →
0.5.0 26 Nov 2014 H1 M1 MIT Yes Details →
0.4.0 05 Nov 2014 H1 M1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1

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 lazysizes

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7642: Cross-site scripting in lazysizes 5.4 medium 5.2.1 10 Dec 2021
Cross-Site Scripting in lazysizes N/A high 5.2.1-rc1 03 Sep 2020

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 lazysizes

Is lazysizes safe to use?

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

Vulert scores lazysizes 68/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 lazysizes affected?

No. 5.3.2, 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 lazysizes should I use?

5.3.2 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 lazysizes have?

2 vulnerabilities are recorded for lazysizes in the npm ecosystem: 0 critical, 1 high, 1 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 lazysizes vulnerabilities disclosed?

0 vulnerabilities were recorded for lazysizes in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 lazysizes 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 lazysizes for upcoming vulnerabilities?

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