VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

bl: vulnerability history, versions and safety

bl is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 29 releases, from Jun 2019 to Sep 2020. 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 M2
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 bl vulnerabilities

Vulert verdict on bl 7.0.13 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 7.0.13 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 02 Sep 2020 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 61 packages i
  • Stars 442 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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.

01 Versions

Which versions are affected

Every version Vulert tracks for bl, 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
7.0.13 19 Oct 2026 none MIT — Details →
7.0.12 30 Jul 2026 none MIT — Details →
7.0.11 29 Jul 2026 none MIT — Details →
7.0.10 27 Jul 2026 none MIT — Details →
7.0.9 27 Jul 2026 none MIT — Details →
7.0.8 23 Jul 2026 none MIT — Details →
7.0.7 20 Jul 2026 none MIT — Details →
7.0.6 02 Jul 2026 none MIT — Details →
7.0.5 29 Jun 2026 none MIT — Details →
7.0.4 22 Jun 2026 none MIT — Details →
7.0.3 04 Jun 2026 none MIT — Details →
7.0.2 30 Apr 2026 none MIT — Details →
7.0.1 28 Apr 2026 none MIT — Details →
7.0.0 14 Apr 2026 none MIT — Details →
6.1.6 04 Dec 2025 none MIT — Details →
6.1.5 24 Nov 2025 none MIT — Details →
6.1.4 15 Oct 2025 none MIT — Details →
6.1.3 05 Sep 2025 none MIT — Details →
6.1.2 12 Aug 2025 none MIT — Details →
6.1.1 01 Aug 2025 none MIT — Details →
6.1.0 11 Mar 2025 none MIT — Details →
6.0.20 03 Mar 2025 none MIT — Details →
6.0.19 28 Jan 2025 none MIT — Details →
6.0.18 30 Dec 2024 none MIT — Details →
6.0.17 30 Dec 2024 none MIT — Details →
6.0.16 25 Sep 2024 none MIT — Details →
6.0.15 10 Sep 2024 none MIT — Details →
6.0.14 10 Jul 2024 none MIT — Details →
6.0.13 21 Jun 2024 none MIT — Details →
6.0.12 07 Mar 2024 none MIT — Details →
6.0.11 08 Feb 2024 none MIT — Details →
6.0.10 01 Jan 2024 none MIT — Details →
6.0.9 27 Nov 2023 none MIT — Details →
6.0.8 25 Oct 2023 none MIT — Details →
6.0.7 25 Aug 2023 none MIT — Details →
6.0.6 18 Aug 2023 none MIT — Details →
6.0.5 15 Aug 2023 none MIT — Details →
6.0.4 07 Aug 2023 none MIT — Details →
6.0.3 07 Jul 2023 none MIT — Details →
6.0.2 05 Jun 2023 none MIT — Details →
6.0.1 17 Mar 2023 none MIT — Details →
6.0.0 19 Oct 2022 none MIT — Details →
5.1.0 18 Oct 2022 none MIT — Details →
5.0.0 02 Apr 2021 none MIT — Details →
4.1.0 09 Feb 2021 none MIT — Details →
4.0.4 04 Feb 2021 none MIT — Details →
1.2.3 03 Sep 2020 none MIT — Details →
2.2.1 26 Aug 2020 none MIT — Details →
3.0.1 26 Aug 2020 none MIT — Details →
4.0.3 26 Aug 2020 none MIT — Details →
4.0.2 18 Mar 2020 none MIT — Details →
4.0.1 04 Mar 2020 none MIT — Details →
4.0.0 19 Sep 2019 none MIT — Details →
3.0.0 28 Feb 2019 none MIT — Details →
2.2.0 03 Feb 2019 none MIT — Details →
2.1.2 12 Oct 2018 none MIT — Details →
2.1.1 08 Oct 2018 none MIT — Details →
2.1.0 04 Oct 2018 none MIT — Details →
2.0.1 14 Jun 2018 none MIT — Details →
2.0.0 15 May 2018 none MIT — Details →
1.2.2 21 Mar 2018 M1 MIT Yes Details →
1.2.1 01 May 2017 M1 MIT Yes Details →
1.2.0 22 Dec 2016 M1 MIT Yes Details →
1.1.2 12 Feb 2016 M1 MIT Yes Details →
1.1.1 12 Feb 2016 M1 MIT Yes Details →
1.0.3 11 Feb 2016 M1 MIT Yes Details →
1.0.2 03 Feb 2016 M1 MIT Yes Details →
0.9.5 19 Jan 2016 M1 MIT Yes Details →
1.0.1 19 Jan 2016 M1 MIT Yes Details →
1.0.0 21 Jun 2015 M1 MIT Yes Details →
0.9.4 19 Jan 2015 M2 MIT Yes Details →
0.9.3 10 Sep 2014 M2 MIT Yes Details →
0.9.2 10 Sep 2014 M2 MIT Yes Details →
0.9.1 20 Aug 2014 M2 MIT Yes Details →
0.9.0 22 Jul 2014 M2 MIT Yes Details →
0.8.2 28 Jun 2014 M2 MIT Yes Details →
0.8.1 27 Jun 2014 M2 MIT Yes Details →
0.8.0 07 Apr 2014 M2 MIT Yes Details →
0.7.0 09 Jan 2014 M2 MIT Yes Details →
0.6.0 03 Dec 2013 M2 MIT Yes Details →
0.5.0 10 Oct 2013 M2 MIT Yes Details →
0.4.2 02 Oct 2013 M2 MIT Yes Details →
0.4.1 08 Aug 2013 M2 MIT Yes Details →
0.4.0 08 Aug 2013 M2 MIT Yes Details →
0.3.0 07 Aug 2013 M2 MIT Yes Details →
0.2.0 23 Jul 2013 M2 MIT Yes Details →
0.1.1 16 Jun 2013 M2 MIT Yes Details →
0.1.0 16 Jun 2013 M2 MIT Yes Details →
0.0.0 15 Jun 2013 M2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 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 bl

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8244: Remote Memory Exposure in bl 6.5 medium 1.2.3 02 Sep 2020
Memory Exposure Vulnerability in bl N/A medium 0.9.5 03 Jun 2019

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 bl

Is bl safe to use?

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

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

No. 7.0.13, 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 bl have?

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

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

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