VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

qsharp-lang: vulnerability history, versions and safety

qsharp-lang 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 qsharp-lang vulnerabilities

Vulert verdict on qsharp-lang 1.33.1 i

Updated on 23 Oct 2026

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

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 1.33.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,024 i
  • Last release this month 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 qsharp-lang, 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
1.33.1 08 Oct 2026 none MIT — Details →
1.33.0 06 Oct 2026 none MIT — Details →
1.32.7-dev 02 Oct 2026 none MIT — Details →
1.32.6-dev 30 Sep 2026 none MIT — Details →
1.32.5-dev 18 Sep 2026 none MIT — Details →
1.32.4-dev 11 Sep 2026 none MIT — Details →
1.32.3 11 Sep 2026 none MIT — Details →
1.32.2-dev 10 Sep 2026 none MIT — Details →
1.32.1-dev 04 Sep 2026 none MIT — Details →
1.32.0 03 Sep 2026 none MIT — Details →
1.31.8-dev 02 Sep 2026 none MIT — Details →
1.31.7-dev 01 Sep 2026 none MIT — Details →
1.31.6-dev 28 Aug 2026 none MIT — Details →
1.31.5-dev 26 Aug 2026 none MIT — Details →
1.31.4-dev 26 Aug 2026 none MIT — Details →
1.31.3-dev 20 Aug 2026 none MIT — Details →
1.31.2-dev 19 Aug 2026 none MIT — Details →
1.31.1-dev 19 Aug 2026 none MIT — Details →
1.31.0 31 Jul 2026 none MIT — Details →
1.30.4-dev 29 Jul 2026 none MIT — Details →
1.30.3-dev 24 Jul 2026 none MIT — Details →
1.30.2-dev 21 Jul 2026 none MIT — Details →
1.30.1-dev 20 Jul 2026 none MIT — Details →
1.30.0 09 Jul 2026 none MIT — Details →
1.29.7-dev 08 Jul 2026 none MIT — Details →
1.29.6-dev 08 Jul 2026 none MIT — Details →
1.29.5-dev 25 Jun 2026 none MIT — Details →
1.29.4-dev 20 Jun 2026 none MIT — Details →
1.29.3-dev 10 Jun 2026 none MIT — Details →
1.29.2-dev 26 May 2026 none MIT — Details →
1.29.1 23 May 2026 none MIT — Details →
1.29.0-dev 23 May 2026 none MIT — Details →
1.28.7-dev 22 May 2026 none MIT — Details →
1.28.6-dev 20 May 2026 none MIT — Details →
1.28.5-dev 18 May 2026 none MIT — Details →
1.28.4-dev 15 May 2026 none MIT — Details →
1.28.3-dev 13 May 2026 none MIT — Details →
1.28.2-dev 11 May 2026 none MIT — Details →
1.28.1-dev 30 Apr 2026 none MIT — Details →
1.28.0 29 Apr 2026 none MIT — Details →
1.27.5-dev 28 Apr 2026 none MIT — Details →
1.27.4-dev 23 Apr 2026 none MIT — Details →
1.27.3-dev 21 Apr 2026 none MIT — Details →
1.27.2-dev 15 Apr 2026 none MIT — Details →
1.27.1-dev 13 Apr 2026 none MIT — Details →
1.27.0 31 Mar 2026 none MIT — Details →
1.26.4-dev 27 Mar 2026 none MIT — Details →
1.26.3-dev 24 Mar 2026 none MIT — Details →
1.26.2-dev 10 Mar 2026 none MIT — Details →
1.26.1 10 Mar 2026 none MIT — Details →
1.26.0 28 Feb 2026 none MIT — Details →
1.25.8-dev 27 Feb 2026 none MIT — Details →
1.25.7-dev 20 Feb 2026 none MIT — Details →
1.25.5-dev 19 Feb 2026 none MIT — Details →
1.25.4-dev 11 Feb 2026 none MIT — Details →
1.25.3-dev 03 Feb 2026 none MIT — Details →
1.25.2-dev 23 Jan 2026 none MIT — Details →
1.25.1 23 Jan 2026 none MIT — Details →
1.25.0 22 Jan 2026 none MIT — Details →
1.23.4-dev 21 Jan 2026 none MIT — Details →
1.23.3-dev 18 Jan 2026 none MIT — Details →
1.23.2-dev 17 Jan 2026 none MIT — Details →
1.23.1-dev 09 Dec 2025 none MIT — Details →
1.23.0 09 Dec 2025 none MIT — Details →
1.22.5-dev 05 Dec 2025 none MIT — Details →
1.22.4-dev 25 Nov 2025 none MIT — Details →
1.22.3-dev 13 Nov 2025 none MIT — Details →
1.22.2-dev 11 Nov 2025 none MIT — Details →
1.22.1-dev 31 Oct 2025 none MIT — Details →
1.22.0 31 Oct 2025 none MIT — Details →
1.21.2-dev 31 Oct 2025 none MIT — Details →
1.21.1-dev 02 Oct 2025 none MIT — Details →
1.21.0 01 Oct 2025 none MIT — Details →
1.20.5-dev 30 Sep 2025 none MIT — Details →
1.20.4-dev 24 Sep 2025 none MIT — Details →
1.20.3-dev 12 Sep 2025 none MIT — Details →
1.20.2-dev 10 Sep 2025 none MIT — Details →
1.20.1-dev 08 Sep 2025 none MIT — Details →
1.20.0 26 Aug 2025 none MIT — Details →
1.19.4-dev 21 Aug 2025 none MIT — Details →
1.19.3-dev 20 Aug 2025 none MIT — Details →
1.19.2-dev 15 Aug 2025 none MIT — Details →
1.19.1-dev 13 Aug 2025 none MIT — Details →
1.19.0 25 Jul 2025 none MIT — Details →
1.18.4-dev 24 Jul 2025 none MIT — Details →
1.18.3-dev 17 Jul 2025 none MIT — Details →
1.18.2-dev 16 Jul 2025 none MIT — Details →
1.18.1-dev 16 Jul 2025 none MIT — Details →
1.18.0 24 Jun 2025 none MIT — Details →
1.17.4-dev 20 Jun 2025 none MIT — Details →
1.17.3-dev 18 Jun 2025 none MIT — Details →
1.17.2-dev 18 Jun 2025 none MIT — Details →
1.17.1-dev 28 May 2025 none MIT — Details →
1.17.0 28 May 2025 none MIT — Details →
1.16.6-dev 23 May 2025 none MIT — Details →
1.16.5-dev 22 May 2025 none MIT — Details →
1.16.4-dev 21 May 2025 none MIT — Details →
1.16.3-dev 16 May 2025 none MIT — Details →
1.16.2-dev 14 May 2025 none MIT — Details →
1.16.1-dev 12 May 2025 none MIT — Details →
1.16.0 01 May 2025 none — — Details →
1.15.4-dev 30 Apr 2025 none — — Details →
1.15.3-dev 24 Apr 2025 none — — Details →
1.15.2-dev 18 Apr 2025 none — — Details →
1.15.1-dev 17 Apr 2025 none — — Details →
1.15.0 31 Mar 2025 none — — Details →
1.14.5-dev 31 Mar 2025 none — — Details →
1.14.4-dev 20 Mar 2025 none — — Details →
1.14.3-dev 19 Mar 2025 none — — Details →
1.14.2-dev 06 Mar 2025 none — — Details →
1.14.1-dev 28 Feb 2025 none — — Details →
1.14.0 28 Feb 2025 none — — Details →
1.13.4-dev 24 Feb 2025 none — — Details →
1.13.3-dev 13 Feb 2025 none — — Details →
1.13.2 04 Feb 2025 none — — Details →
1.13.1-dev 31 Jan 2025 none — — Details →
1.13.0 30 Jan 2025 none — — Details →
1.12.5-dev 28 Jan 2025 none — — Details →
1.12.4-dev 25 Jan 2025 none — — Details →
1.12.3-dev 20 Jan 2025 none — — Details →

The newest 120 of 208 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 qsharp-lang

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 qsharp-lang

Is qsharp-lang safe to use?

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

Vulert scores qsharp-lang 85/100, which reads as healthy. 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 qsharp-lang affected?

No. 1.33.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 qsharp-lang have?

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

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

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