Vulnerability Database · npm · Package report

botbuilder-azure: vulnerability history, versions and safety

botbuilder-azure 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 botbuilder-azure 4.23.3 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 4.23.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 5 packages i
  • Stars 722 i
  • OpenSSF scorecard 3/10 i
  • Last release 13 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 botbuilder-azure, 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
4.23.3 27 Aug 2025 none MIT — Details →
4.23.3-dev 19 Aug 2025 none MIT — Details →
4.17.0-blobs1 10 Jun 2025 none MIT — Details →
4.24.0-dev2 09 Apr 2025 none MIT — Details →
4.24.0-dev1 07 Apr 2025 none MIT — Details →
4.23.3-dev2 12 Feb 2025 none MIT — Details →
4.23.3-dev1 11 Feb 2025 none MIT — Details →
4.23.2 06 Feb 2025 none MIT — Details →
4.23.2-rc2 03 Feb 2025 none MIT — Details →
4.23.2-dev1 10 Dec 2024 none MIT — Details →
4.24.0-rc1 16 Oct 2024 none MIT — Details →
4.23.1 23 Sep 2024 none MIT — Details →
4.23.0 28 Aug 2024 none MIT — Details →
4.23.0-rc1 26 Aug 2024 none MIT — Details →
4.22.3 27 Jun 2024 none MIT — Details →
4.22.2 15 Apr 2024 none MIT — Details →
4.23.0-dev.20240405 05 Apr 2024 none MIT — Details →
4.23.0-dev.20240404 04 Apr 2024 none MIT — Details →
4.23.0-dev.20240403 03 Apr 2024 none MIT — Details →
4.17.0-spike1 01 Apr 2024 none MIT — Details →
4.23.0-dev.20240329 29 Mar 2024 none MIT — Details →
4.23.0-dev.20240320 20 Mar 2024 none MIT — Details →
4.17.0-dev1 14 Mar 2024 none MIT — Details →
4.22.2-rc2 14 Mar 2024 none MIT — Details →
4.23.0-dev.20240307 07 Mar 2024 none MIT — Details →
4.14.1-dev8 06 Mar 2024 none MIT — Details →
4.23.0-dev.20240202 02 Feb 2024 none MIT — Details →
4.23.0-dev.20240130 30 Jan 2024 none MIT — Details →
4.22.2-rc1 29 Jan 2024 none MIT — Details →
4.22.1 29 Jan 2024 none MIT — Details →
4.23.0-dev.20240126 26 Jan 2024 none MIT — Details →
4.22.0 25 Jan 2024 none MIT — Details →
4.22.0-dev.20240125.05ca65f 25 Jan 2024 none MIT — Details →
4.14.1-dev7 24 Jan 2024 none MIT — Details →
4.21.5-rc 24 Jan 2024 none MIT — Details →
4.22.0-dev.20240122.6b2656b 22 Jan 2024 none MIT — Details →
4.22.0-dev.20240119.7675c41 19 Jan 2024 none MIT — Details →
4.22.0-dev.20240117.20c0c2f 17 Jan 2024 none MIT — Details →
4.14.1-dev6 16 Jan 2024 none MIT — Details →
4.22.0-dev.20240110.8a30768 10 Jan 2024 none MIT — Details →
4.22.0-dev.20240109.3418fa9 09 Jan 2024 none MIT — Details →
4.21.4 08 Jan 2024 none MIT — Details →
4.14.1-dev5 26 Dec 2023 none MIT — Details →
4.21.4-rc2 26 Dec 2023 none MIT — Details →
4.22.0-dev.20231225.709a823 25 Dec 2023 none MIT — Details →
4.22.0-dev.20231222.6efb46d 22 Dec 2023 none MIT — Details →
4.21.4-rc 21 Dec 2023 none MIT — Details →
4.22.0-dev.20231221.6efb46d 21 Dec 2023 none MIT — Details →
4.22.0-dev.20231220.685bdd2 20 Dec 2023 none MIT — Details →
4.14.1-dev4 19 Dec 2023 none MIT — Details →
4.22.0-dev.20231219.685bdd2 19 Dec 2023 none MIT — Details →
4.21.4-dev2 18 Dec 2023 none MIT — Details →
4.14.1-dev3 14 Dec 2023 none MIT — Details →
4.21.4-dev 12 Dec 2023 none MIT — Details →
4.22.0-dev.20231208.f3db3e9 08 Dec 2023 none MIT — Details →
4.21.3 07 Dec 2023 none MIT — Details →
4.21.3-rc 07 Dec 2023 none MIT — Details →
4.22.0-dev.20231201.363e0c9 01 Dec 2023 none MIT — Details →
4.21.2 30 Nov 2023 none MIT — Details →
4.14.1-dev2 17 Nov 2023 none MIT — Details →
4.20.3 16 Nov 2023 none MIT — Details →
4.22.0-dev.20231115.60824fe 15 Nov 2023 none MIT — Details →
4.22.0-dev.20231114.e0e656b 14 Nov 2023 none MIT — Details →
4.22.0-dev.20231113.45d7dda 13 Nov 2023 none MIT — Details →
4.21.1 09 Nov 2023 none MIT — Details →
4.14.1-dev1 09 Nov 2023 none MIT — Details →
4.21.1-rc2 09 Nov 2023 none MIT — Details →
4.21.1-rc 09 Nov 2023 none MIT — Details →
4.22.0-dev.20231109.6abfddf 09 Nov 2023 none MIT — Details →
4.20.2 03 Nov 2023 none MIT — Details →
4.22.0-dev.20231103.7277636 03 Nov 2023 none MIT — Details →
4.22.0-dev.20231102.d18c19c 02 Nov 2023 none MIT — Details →
4.22.0-dev.20231101.0032ed7 01 Nov 2023 none MIT — Details →
4.22.0-dev.20231031.0032ed7 31 Oct 2023 none MIT — Details →
4.22.0-dev.20231030.663bc95 30 Oct 2023 none MIT — Details →
4.22.0-dev.20231026.593cd3b 26 Oct 2023 none MIT — Details →
4.21.0 25 Oct 2023 none MIT — Details →
4.21.0-dev.20231024.593cd3b 24 Oct 2023 none MIT — Details →
4.21.0-dev.20231023.593cd3b 23 Oct 2023 none MIT — Details →
4.21.0-dev.20231020.c288fc7 20 Oct 2023 none MIT — Details →
4.21.0-dev.20231019.c288fc7 19 Oct 2023 none MIT — Details →
4.21.0-dev.20231018.5e5d819 18 Oct 2023 none MIT — Details →
4.21.0-dev.20231017.6583ddc 17 Oct 2023 none MIT — Details →
4.21.0-dev.20231011.dec8115 11 Oct 2023 none MIT — Details →
4.21.0-dev.20231010.123cc88 10 Oct 2023 none MIT — Details →
4.20.1 19 Sep 2023 none MIT — Details →
4.20.1-rc 18 Sep 2023 none MIT — Details →
4.21.0-dev.20230911.cbb187d 11 Sep 2023 none MIT — Details →
4.21.0-dev.20230907.3685e5e 07 Sep 2023 none MIT — Details →
4.21.0-dev.20230825.81e2d98 25 Aug 2023 none MIT — Details →
4.21.0-dev.20230822.7110e8a 22 Aug 2023 none MIT — Details →
4.21.0-dev.20230818.447c81c 18 Aug 2023 none MIT — Details →
4.21.0-dev.20230809.5b58d10 09 Aug 2023 none MIT — Details →
4.21.0-dev.20230808.5b58d10 08 Aug 2023 none MIT — Details →
4.21.0-dev.20230808.e51063d 08 Aug 2023 none MIT — Details →
4.21.0-dev.20230807.e51063d 07 Aug 2023 none MIT — Details →
4.21.0-dev.20230802.e402eca 02 Aug 2023 none MIT — Details →
4.21.0-dev.20230731.51016a6 31 Jul 2023 none MIT — Details →
4.21.0-dev.20230724.faf57c5 24 Jul 2023 none MIT — Details →
4.21.0-dev.20230721.f21e7cc 21 Jul 2023 none MIT — Details →
4.21.0-dev.20230628.288cb8f 28 Jun 2023 none — — Details →
4.21.0-dev.20230623.288cb8f 23 Jun 2023 none — — Details →
4.21.0-dev.20230612.5ee34c0 12 Jun 2023 none — — Details →
4.20.0 01 Jun 2023 none — — Details →
4.21.0-dev.20230531.1b967e3 31 May 2023 none — — Details →
4.20.0-rc 30 May 2023 none — — Details →
4.20.0-dev.20230517.6c30afa 17 May 2023 none — — Details →
4.20.0-dev.20230510.192d4b2 10 May 2023 none — — Details →
4.20.0-dev.20230508.c2abd7d 08 May 2023 none — — Details →
4.20.0-dev.20230505.c2abd7d 05 May 2023 none — — Details →
4.20.0-dev.20230504.561d438 04 May 2023 none — — Details →
4.20.0-ww.20230425 25 Apr 2023 none — — Details →
4.20.0-dev.20230425 25 Apr 2023 none — — Details →
4.20.0-dev.20230425.25e7146 25 Apr 2023 none — — Details →
4.20.0-dev.20230421 21 Apr 2023 none — — Details →
4.20.0-dev.20230322.f9cf5fd 22 Mar 2023 none — — Details →
4.19.3 21 Mar 2023 none — — Details →
4.19.3-rc5 21 Mar 2023 none — — Details →
4.19.3-rc4 17 Mar 2023 none — — Details →
4.19.3-rc2 16 Mar 2023 none — — Details →

The newest 120 of 561 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 botbuilder-azure

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 botbuilder-azure

Is botbuilder-azure safe to use?

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

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

No. 4.23.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 botbuilder-azure should I use?

4.23.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 botbuilder-azure have?

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

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

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