Vulnerability Database · npm · Package report

tiny-lru: vulnerability history, versions and safety

Q: How do I monitor tiny-lru for upcoming vulnerabilities?

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

tiny-lru is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 tiny-lru vulnerabilities

Vulert verdict on tiny-lru 13.1.1 i

Updated on 23 Oct 2026

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

Package health score 76/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Quiet

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

Current release 13.1.1 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 284 packages i
Stars 184 i
OpenSSF scorecard 3/10 i
Last release this month i
Licence BSD-3-Clause 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for tiny-lru, 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
13.1.1	21 Oct 2026	none	BSD-3-Clause	—	Details →
13.1.0	27 Sep 2026	none	BSD-3-Clause	—	Details →
13.0.1	15 Sep 2026	none	BSD-3-Clause	—	Details →
13.0.0	29 Mar 2026	none	BSD-3-Clause	—	Details →
12.0.0	29 Mar 2026	none	BSD-3-Clause	—	Details →
11.4.7	14 Jan 2026	none	BSD-3-Clause	—	Details →
11.4.6	14 Jan 2026	none	BSD-3-Clause	—	Details →
11.4.5	13 Aug 2025	none	BSD-3-Clause	—	Details →
11.4.4	13 Aug 2025	none	BSD-3-Clause	—	Details →
11.4.3	10 Aug 2025	none	BSD-3-Clause	—	Details →
11.4.2	10 Aug 2025	none	BSD-3-Clause	—	Details →
11.4.1	10 Aug 2025	none	BSD-3-Clause	—	Details →
11.4.0	09 Aug 2025	none	BSD-3-Clause	—	Details →
11.3.4	16 Jul 2025	none	BSD-3-Clause	—	Details →
11.3.3	18 Jun 2025	none	BSD-3-Clause	—	Details →
11.3.2	19 May 2025	none	BSD-3-Clause	—	Details →
11.3.1	17 May 2025	none	BSD-3-Clause	—	Details →
11.3.0	17 May 2025	none	BSD-3-Clause	—	Details →
11.2.11	06 Jul 2024	none	BSD-3-Clause	—	Details →
11.2.10	06 Jul 2024	none	BSD-3-Clause	—	Details →
11.2.9	06 Jul 2024	none	BSD-3-Clause	—	Details →
11.2.8	06 Jul 2024	none	BSD-3-Clause	—	Details →
11.2.7	06 Jul 2024	none	BSD-3-Clause	—	Details →
11.2.6	16 Apr 2024	none	BSD-3-Clause	—	Details →
11.2.5	29 Oct 2023	none	BSD-3-Clause	—	Details →
11.2.4	29 Oct 2023	none	BSD-3-Clause	—	Details →
11.2.3	10 Oct 2023	none	BSD-3-Clause	—	Details →
11.2.2	04 Oct 2023	none	BSD-3-Clause	—	Details →
11.2.1	04 Oct 2023	none	BSD-3-Clause	—	Details →
11.2.0	29 Sep 2023	none	BSD-3-Clause	—	Details →
11.1.2	21 Sep 2023	none	BSD-3-Clause	—	Details →
11.1.1	21 Sep 2023	none	BSD-3-Clause	—	Details →
11.1.0	21 Sep 2023	none	BSD-3-Clause	—	Details →
11.0.1	20 Apr 2023	none	BSD-3-Clause	—	Details →
11.0.0	07 Apr 2023	none	BSD-3-Clause	—	Details →
10.4.1	02 Apr 2023	none	BSD-3-Clause	—	Details →
10.4.0	02 Apr 2023	none	BSD-3-Clause	—	Details →
10.3.0	23 Mar 2023	none	BSD-3-Clause	—	Details →
10.2.2	17 Mar 2023	none	BSD-3-Clause	—	Details →
10.2.1	14 Mar 2023	none	BSD-3-Clause	—	Details →
10.2.0	14 Mar 2023	none	BSD-3-Clause	—	Details →
10.1.1	13 Mar 2023	none	BSD-3-Clause	—	Details →
10.1.0	13 Mar 2023	none	BSD-3-Clause	—	Details →
10.0.1	01 Nov 2022	none	BSD-3-Clause	—	Details →
10.0.0	28 Oct 2022	none	BSD-3-Clause	—	Details →
9.0.3	05 Oct 2022	none	BSD-3-Clause	—	Details →
9.0.2	23 Sep 2022	none	BSD-3-Clause	—	Details →
9.0.1	21 Sep 2022	none	BSD-3-Clause	—	Details →
9.0.0	21 Sep 2022	none	BSD-3-Clause	—	Details →
8.0.2	12 Mar 2022	none	BSD-3-Clause	—	Details →
8.0.1	13 Feb 2022	none	BSD-3-Clause	—	Details →
8.0.0	13 Feb 2022	none	BSD-3-Clause	—	Details →
7.0.6	06 Jun 2020	none	BSD-3-Clause	—	Details →
7.0.5	06 Jun 2020	none	BSD-3-Clause	—	Details →
7.0.4	29 May 2020	none	BSD-3-Clause	—	Details →
7.0.3	29 May 2020	none	BSD-3-Clause	—	Details →
7.0.2	31 Oct 2019	none	BSD-3-Clause	—	Details →
7.0.1	08 Oct 2019	none	BSD-3-Clause	—	Details →
7.0.0	27 Sep 2019	none	BSD-3-Clause	—	Details →
6.1.0	19 Sep 2019	none	BSD-3-Clause	—	Details →
6.0.1	30 Jan 2019	none	BSD-3-Clause	—	Details →
6.0.0	22 Jan 2019	none	BSD-3-Clause	—	Details →
5.1.4	13 Jan 2019	none	BSD-3-Clause	—	Details →
5.1.3	13 Jan 2019	none	BSD-3-Clause	—	Details →
5.1.2	13 Jan 2019	none	BSD-3-Clause	—	Details →
5.1.1	13 Jan 2019	none	BSD-3-Clause	—	Details →
5.1.0	13 Jan 2019	none	BSD-3-Clause	—	Details →
5.0.7	13 Jan 2019	none	BSD-3-Clause	—	Details →
5.0.6	31 Dec 2018	none	BSD-3-Clause	—	Details →
5.0.4	20 Dec 2018	none	BSD-3-Clause	—	Details →
5.0.3	13 Dec 2018	none	BSD-3-Clause	—	Details →
5.0.2	12 Dec 2018	none	BSD-3-Clause	—	Details →
5.0.1	12 Dec 2018	none	BSD-3-Clause	—	Details →
5.0.0	09 Dec 2018	none	BSD-3-Clause	—	Details →
4.0.6	08 Dec 2018	none	BSD-3-Clause	—	Details →
4.0.5	07 Dec 2018	none	BSD-3-Clause	—	Details →
4.0.4	06 Dec 2018	none	BSD-3-Clause	—	Details →
4.0.3	06 Dec 2018	none	BSD-3-Clause	—	Details →
4.0.2	05 Dec 2018	none	BSD-3-Clause	—	Details →
4.0.1	05 Dec 2018	none	BSD-3-Clause	—	Details →
4.0.0	05 Dec 2018	none	BSD-3-Clause	—	Details →
3.0.7	05 Dec 2018	none	BSD-3-Clause	—	Details →
3.0.6	05 Dec 2018	none	BSD-3-Clause	—	Details →
3.0.5	30 Nov 2018	none	BSD-3-Clause	—	Details →
3.0.4	27 Nov 2018	none	BSD-3-Clause	—	Details →
3.0.3	26 Nov 2018	none	BSD-3-Clause	—	Details →
3.0.2	26 Nov 2018	none	BSD-3-Clause	—	Details →
3.0.1	24 Nov 2018	none	BSD-3-Clause	—	Details →
3.0.0	24 Nov 2018	none	BSD-3-Clause	—	Details →
2.0.0	21 Nov 2018	none	BSD-3-Clause	—	Details →
1.6.4	21 Nov 2018	none	BSD-3-Clause	—	Details →
1.6.3	20 Nov 2018	none	BSD-3-Clause	—	Details →
1.6.2	20 Nov 2018	none	BSD-3-Clause	—	Details →
1.6.1	24 May 2018	none	BSD-3-Clause	—	Details →
1.6.0	23 May 2018	none	BSD-3-Clause	—	Details →
1.5.2	28 Mar 2018	none	BSD-3-Clause	—	Details →
1.5.1	25 Mar 2018	none	BSD-3-Clause	—	Details →
1.5.0	28 Dec 2017	none	BSD-3-Clause	—	Details →
1.4.13	13 Nov 2017	none	BSD-3-Clause	—	Details →
1.4.12	12 Nov 2017	none	BSD-3-Clause	—	Details →
1.4.11	06 Nov 2017	none	—	—	Details →
1.4.10	09 Oct 2017	none	—	—	Details →
1.4.9	13 May 2017	none	—	—	Details →
1.4.8	11 Apr 2017	none	—	—	Details →
1.4.7	10 Feb 2017	none	—	—	Details →
1.4.6	10 Feb 2017	none	—	—	Details →
1.4.5	10 Feb 2017	none	—	—	Details →
1.4.4	10 Feb 2017	none	—	—	Details →
1.4.3	10 Feb 2017	none	—	—	Details →
1.4.2	23 Jan 2017	none	—	—	Details →
1.4.1	06 Jan 2017	none	—	—	Details →
1.4.0	03 Jan 2017	none	—	—	Details →
1.3.3	20 Nov 2016	none	—	—	Details →
1.3.2	20 Nov 2016	none	—	—	Details →
1.3.1	19 Nov 2016	none	—	—	Details →
1.3.0	19 Nov 2016	none	—	—	Details →
1.1.0	24 Jan 2016	none	—	—	Details →
1.0.2	26 Aug 2013	none	—	—	Details →
1.0.1	28 Jul 2013	none	—	—	Details →
1.0.0	26 Jul 2013	none	—	—	Details →

All 120 versions Vulert tracks for this package. 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for tiny-lru

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

Is tiny-lru safe to use?

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

Vulert scores tiny-lru 76/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 tiny-lru affected?

No. 13.1.1, 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.

How many vulnerabilities does tiny-lru have?

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

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

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