Vulnerability Database · npm · Package report

lru-cache: vulnerability history, versions and safety

lru-cache 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.

Vulert verdict on lru-cache 11.5.3 i

Updated on 23 Oct 2026

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

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

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

  • Current release 11.5.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 88,950 packages i
  • Stars 5,918 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence BlueOak-1.0.0 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 lru-cache, 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
11.5.3 18 Sep 2026 none BlueOak-1.0.0 — Details →
11.5.2 07 Jul 2026 none BlueOak-1.0.0 — Details →
11.5.1 27 May 2026 none BlueOak-1.0.0 — Details →
11.5.0 19 May 2026 none BlueOak-1.0.0 — Details →
11.4.0 18 May 2026 none BlueOak-1.0.0 — Details →
11.3.6 04 May 2026 none BlueOak-1.0.0 — Details →
11.3.5 13 Apr 2026 none BlueOak-1.0.0 — Details →
11.3.4 13 Apr 2026 none BlueOak-1.0.0 — Details →
11.3.3 08 Apr 2026 none BlueOak-1.0.0 — Details →
11.3.2 06 Apr 2026 none BlueOak-1.0.0 — Details →
11.3.1 06 Apr 2026 none BlueOak-1.0.0 — Details →
11.3.0 06 Apr 2026 none BlueOak-1.0.0 — Details →
11.2.7 13 Mar 2026 none BlueOak-1.0.0 — Details →
11.2.6 10 Feb 2026 none BlueOak-1.0.0 — Details →
11.2.5 26 Jan 2026 none BlueOak-1.0.0 — Details →
11.2.4 30 Nov 2025 none BlueOak-1.0.0 — Details →
11.2.3 30 Nov 2025 none BlueOak-1.0.0 — Details →
11.2.2 23 Sep 2025 none ISC — Details →
11.2.1 03 Sep 2025 none ISC — Details →
11.2.0 03 Sep 2025 none ISC — Details →
11.1.0 24 Mar 2025 none ISC — Details →
11.0.2 31 Oct 2024 none ISC — Details →
11.0.1 06 Sep 2024 none ISC — Details →
10.4.3 09 Jul 2024 none ISC — Details →
10.4.2 09 Jul 2024 none ISC — Details →
11.0.0 08 Jul 2024 none ISC — Details →
10.4.1 08 Jul 2024 none ISC — Details →
10.4.0 08 Jul 2024 none ISC — Details →
10.3.1 06 Jul 2024 none ISC — Details →
10.3.0 28 Jun 2024 none ISC — Details →
10.2.2 28 Apr 2024 none ISC — Details →
10.2.1 25 Apr 2024 none ISC — Details →
10.2.0 25 Jan 2024 none ISC — Details →
10.1.0 22 Nov 2023 none ISC — Details →
10.0.3 19 Nov 2023 none ISC — Details →
10.0.2 10 Nov 2023 none ISC — Details →
10.0.1 10 Aug 2023 none ISC — Details →
10.0.0 15 Jun 2023 none ISC — Details →
9.1.2 01 Jun 2023 none ISC — Details →
9.1.1 23 Apr 2023 none ISC — Details →
9.1.0 18 Apr 2023 none ISC — Details →
9.0.3 14 Apr 2023 none ISC — Details →
9.0.2 13 Apr 2023 none ISC — Details →
9.0.1 10 Apr 2023 none ISC — Details →
9.0.0 09 Apr 2023 none ISC — Details →
8.0.5 05 Apr 2023 none ISC — Details →
8.0.4 17 Mar 2023 none ISC — Details →
8.0.3 15 Mar 2023 none ISC — Details →
8.0.2 15 Mar 2023 none ISC — Details →
8.0.1 15 Mar 2023 none ISC — Details →
8.0.0 12 Mar 2023 none ISC — Details →
7.18.3 05 Mar 2023 none ISC — Details →
7.18.2 05 Mar 2023 none ISC — Details →
7.18.1 01 Mar 2023 none ISC — Details →
7.17.2 01 Mar 2023 none ISC — Details →
7.18.0 01 Mar 2023 none ISC — Details →
7.17.1 01 Mar 2023 none ISC — Details →
7.17.0 22 Feb 2023 none ISC — Details →
7.16.2 21 Feb 2023 none ISC — Details →
7.16.1 17 Feb 2023 none ISC — Details →
7.16.0 16 Feb 2023 none ISC — Details →
7.15.0 16 Feb 2023 none ISC — Details →
7.14.1 02 Nov 2022 none ISC — Details →
7.14.0 16 Aug 2022 none ISC — Details →
7.13.2 02 Aug 2022 none ISC — Details →
7.13.1 14 Jul 2022 none ISC — Details →
7.13.0 12 Jul 2022 none ISC — Details →
7.12.1 12 Jul 2022 none ISC — Details →
7.12.0 29 Jun 2022 none ISC — Details →
7.11.0 29 Jun 2022 none ISC — Details →
7.10.3 29 Jun 2022 none ISC — Details →
7.10.2 23 Jun 2022 none ISC — Details →
7.10.1 11 May 2022 none ISC — Details →
7.10.0 11 May 2022 none ISC — Details →
7.9.1 11 May 2022 none ISC — Details →
7.9.0 30 Apr 2022 none ISC — Details →
7.8.2 30 Apr 2022 none ISC — Details →
7.0.4 09 Apr 2022 none ISC — Details →
7.1.3 09 Apr 2022 none ISC — Details →
7.2.3 09 Apr 2022 none ISC — Details →
7.3.3 09 Apr 2022 none ISC — Details →
7.4.5 09 Apr 2022 none ISC — Details →
7.5.2 09 Apr 2022 none ISC — Details →
7.6.1 09 Apr 2022 none ISC — Details →
7.7.4 09 Apr 2022 none ISC — Details →
7.8.1 09 Apr 2022 none ISC — Details →
7.8.0 07 Apr 2022 none ISC — Details →
7.7.3 30 Mar 2022 none ISC — Details →
7.7.2 29 Mar 2022 none ISC — Details →
7.7.1 18 Mar 2022 none ISC — Details →
7.7.0 17 Mar 2022 none ISC — Details →
7.6.0 17 Mar 2022 none ISC — Details →
7.5.1 14 Mar 2022 none ISC — Details →
7.5.0 14 Mar 2022 none ISC — Details →
7.0.3 10 Mar 2022 none ISC — Details →
7.1.2 10 Mar 2022 none ISC — Details →
7.2.2 10 Mar 2022 none ISC — Details →
7.3.2 10 Mar 2022 none ISC — Details →
7.4.4 10 Mar 2022 none ISC — Details →
7.4.3 10 Mar 2022 none ISC — Details →
7.4.2 09 Mar 2022 none — — Details →
7.4.1 05 Mar 2022 none — — Details →
7.4.0 22 Feb 2022 none — — Details →
7.0.2 09 Feb 2022 none — — Details →
7.1.1 09 Feb 2022 none — — Details →
7.2.1 09 Feb 2022 none — — Details →
7.3.1 09 Feb 2022 none — — Details →
7.3.0 09 Feb 2022 none — — Details →
7.2.0 08 Feb 2022 none — — Details →
7.1.0 08 Feb 2022 none — — Details →
7.0.1 08 Feb 2022 none — — Details →
7.0.0 08 Feb 2022 none — — Details →
6.0.0 11 Jul 2020 none — — Details →
4.1.5 29 Nov 2018 none — — Details →
5.1.1 21 Nov 2018 none — — Details →
5.1.0 21 Nov 2018 none — — Details →
5.0.1 21 Nov 2018 none — — Details →
5.0.0 21 Nov 2018 none — — Details →
4.1.4 21 Nov 2018 none — — Details →
4.1.3 07 May 2018 none — — Details →

The newest 120 of 164 versions Vulert tracks. 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 lru-cache

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 lru-cache

Is lru-cache safe to use?

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

Vulert scores lru-cache 84/100, which reads as in good shape. 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 lru-cache affected?

No. 11.5.3, 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 lru-cache should I use?

11.5.3 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 lru-cache have?

0 vulnerabilities are recorded for lru-cache 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 lru-cache vulnerabilities disclosed?

0 vulnerabilities were recorded for lru-cache 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 lru-cache 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 lru-cache for upcoming vulnerabilities?

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