VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

bottleneck: vulnerability history, versions and safety

bottleneck 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.

See all bottleneck vulnerabilities

Vulert verdict on bottleneck 2.19.5 i

Updated on 23 Oct 2026

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

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Inactive

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

  • Current release 2.19.5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 6,737 packages i
  • Stars 2,006 i
  • OpenSSF scorecard 1/10 i
  • Last release 86 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 bottleneck, 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
2.19.5 03 Aug 2019 none MIT — Details →
2.19.4 17 Jul 2019 none MIT — Details →
2.19.3 16 Jul 2019 none MIT — Details →
2.19.2 06 Jul 2019 none MIT — Details →
2.19.1 08 Jun 2019 none MIT — Details →
2.19.0 01 Jun 2019 none MIT — Details →
2.18.1 11 May 2019 none MIT — Details →
2.18.0 13 Apr 2019 none MIT — Details →
2.17.1 03 Mar 2019 none MIT — Details →
2.17.0 25 Feb 2019 none MIT — Details →
2.16.2 10 Feb 2019 none MIT — Details →
2.16.1 05 Feb 2019 none MIT — Details →
2.16.0 03 Feb 2019 none MIT — Details →
2.15.3 15 Jan 2019 none MIT — Details →
2.15.2 13 Jan 2019 none MIT — Details →
2.15.1 12 Jan 2019 none MIT — Details →
2.15.0 28 Dec 2018 none MIT — Details →
2.14.1 23 Dec 2018 none MIT — Details →
2.14.0 16 Dec 2018 none MIT — Details →
2.13.2 04 Dec 2018 none MIT — Details →
2.13.1 01 Dec 2018 none MIT — Details →
2.13.0 03 Nov 2018 none MIT — Details →
2.12.2 21 Oct 2018 none MIT — Details →
2.12.1 13 Oct 2018 none MIT — Details →
2.12.0 09 Oct 2018 none MIT — Details →
2.11.2 02 Oct 2018 none MIT — Details →
2.11.1 27 Sep 2018 none MIT — Details →
2.11.0 20 Sep 2018 none MIT — Details →
2.10.0 13 Sep 2018 none MIT — Details →
2.9.0 06 Sep 2018 none MIT — Details →
2.8.0 20 Aug 2018 none MIT — Details →
2.7.2 17 Aug 2018 none MIT — Details →
2.7.1 13 Aug 2018 none MIT — Details →
2.7.0 12 Aug 2018 none MIT — Details →
2.6.0 08 Jul 2018 none MIT — Details →
2.5.1 03 Jul 2018 none MIT — Details →
2.5.0 16 Jun 2018 none MIT — Details →
2.4.0 09 Jun 2018 none MIT — Details →
2.3.1 19 May 2018 none MIT — Details →
2.3.0 08 Apr 2018 none MIT — Details →
2.2.2 24 Mar 2018 none MIT — Details →
2.2.1 18 Mar 2018 none MIT — Details →
2.2.0 13 Mar 2018 none MIT — Details →
2.1.0 22 Feb 2018 none MIT — Details →
2.0.1 16 Jan 2018 none MIT — Details →
2.0.0 14 Jan 2018 none MIT — Details →
1.16.0 19 Jun 2017 none MIT — Details →
1.15.1 19 Jan 2017 none MIT — Details →
1.15.0 30 Oct 2016 none MIT — Details →
1.14.0 05 Oct 2016 none MIT — Details →
1.13.1 25 Sep 2016 none MIT — Details →
1.13.0 25 Sep 2016 none MIT — Details →
1.12.0 07 May 2016 none MIT — Details →
1.11.0 22 Mar 2016 none MIT — Details →
1.10.2 08 Feb 2016 none MIT — Details →
1.10.1 23 Jan 2016 none MIT — Details →
1.10.0 19 Jan 2016 none MIT — Details →
1.9.1 31 Aug 2015 none MIT — Details →
1.9.0 22 Aug 2015 none MIT — Details →
1.8.1 14 Jul 2015 none MIT — Details →
1.8.0 14 Jul 2015 none MIT — Details →
1.7.2 12 Jul 2015 none MIT — Details →
1.7.1 07 May 2015 none MIT — Details →
1.7.0 16 Mar 2015 none MIT — Details →
1.6.0 16 Mar 2015 none MIT — Details →
1.5.3 02 Oct 2014 none MIT — Details →
1.5.2 11 Aug 2014 none MIT — Details →
1.5.1 26 Jul 2014 none MIT — Details →
1.5.0 24 Jul 2014 none MIT — Details →
1.4.1 24 Jul 2014 none MIT — Details →
1.4.0 14 Jul 2014 none MIT — Details →
1.3.1 05 Jul 2014 none MIT — Details →
1.3.0 03 Jul 2014 none MIT — Details →
1.2.0 07 Jun 2014 none MIT — Details →
1.1.2 25 Apr 2014 none MIT — Details →
1.1.1 23 Mar 2014 none MIT — Details →
1.1.0 16 Mar 2014 none MIT — Details →
1.0.0 20 Jan 2014 none MIT — Details →
0.1.0 20 Jan 2014 none MIT — Details →

All 79 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.

03 Vulnerabilities

Recorded vulnerabilities for bottleneck

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 bottleneck

Is bottleneck safe to use?

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

Vulert scores bottleneck 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 bottleneck affected?

No. 2.19.5, 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 bottleneck should I use?

2.19.5 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 bottleneck have?

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

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

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