VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

gql: vulnerability history, versions and safety

gql is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI 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 gql vulnerabilities

Vulert verdict on gql 4.4.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 4.4.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 571 packages i
  • Stars 1,684 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, 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 gql, 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.4.0 27 Sep 2026 none MIT — Details →
4.4.0b1 23 Sep 2026 none MIT — Details →
4.4.0b0 21 Jul 2026 none MIT — Details →
4.3.0b3 30 May 2026 none MIT — Details →
4.3.0b2 02 Apr 2026 none MIT — Details →
4.3.0b1 30 Mar 2026 none MIT — Details →
4.3.0b0 09 Jan 2026 none MIT — Details →
4.2.0b0 05 Sep 2025 none MIT — Details →
4.1.0b0 17 Aug 2025 none MIT — Details →
4.0.0 17 Aug 2025 none MIT — Details →
4.0.0b0 28 May 2025 none MIT — Details →
4.0.0a0 20 May 2025 none MIT — Details →
3.5.3 20 May 2025 none MIT — Details →
3.5.2 06 Mar 2025 none MIT — Details →
3.5.1 19 Feb 2025 none MIT — Details →
3.6.0b4 18 Feb 2025 none MIT — Details →
3.6.0b3 20 Jan 2025 none MIT — Details →
3.6.0b2 14 Apr 2024 none MIT — Details →
3.6.0b1 08 Feb 2024 none MIT — Details →
3.6.0b0 03 Jan 2024 none MIT — Details →
3.5.0 03 Jan 2024 none MIT — Details →
3.5.0b9 15 Dec 2023 none MIT — Details →
3.5.0b8 19 Nov 2023 none MIT — Details →
3.5.0b7 14 Nov 2023 none MIT — Details →
3.5.0b6 04 Oct 2023 none MIT — Details →
3.5.0b5 26 Jul 2023 none MIT — Details →
3.5.0b4 06 May 2023 none MIT — Details →
3.4.1 06 May 2023 none MIT — Details →
3.5.0b3 23 Feb 2023 none MIT — Details →
3.5.0b2 23 Feb 2023 none MIT — Details →
3.5.0b1 22 Feb 2023 none MIT — Details →
3.5.0b0 26 Nov 2022 none MIT — Details →
3.5.0a0 07 Nov 2022 none MIT — Details →
3.4.0 14 Jul 2022 none MIT — Details →
3.3.0 20 May 2022 none MIT — Details →
3.2.0 12 Apr 2022 none MIT — Details →
3.1.0 11 Mar 2022 none MIT — Details →
3.0.0 22 Jan 2022 none MIT — Details →
3.0.0rc1 16 Jan 2022 none MIT — Details →
3.0.0rc0 10 Dec 2021 none MIT — Details →
3.0.0b1 22 Nov 2021 none MIT — Details →
3.0.0b0 26 Oct 2021 none MIT — Details →
3.0.0a6 09 Jun 2021 none MIT — Details →
3.0.0a5 21 Nov 2020 none MIT — Details →
3.0.0a4 01 Nov 2020 none MIT — Details →
3.0.0a3 15 Oct 2020 none MIT — Details →
3.0.0a2 04 Oct 2020 none MIT — Details →
3.0.0a1 13 Jul 2020 none MIT — Details →
3.0.0a0 17 May 2020 none MIT — Details →
2.0.0 17 May 2020 none MIT — Details →
0.5.0 10 May 2020 none MIT — Details →
0.4.0 10 May 2020 none MIT — Details →
0.3.0 24 Jan 2020 none MIT — Details →
0.2.0 29 Dec 2019 none MIT — Details →
0.1.0 06 Aug 2016 none MIT — Details →

All 55 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 gql

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 gql

Is gql safe to use?

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

Vulert scores gql 82/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 gql affected?

No. 4.4.0, 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 gql should I use?

4.4.0 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 gql have?

0 vulnerabilities are recorded for gql in the PyPI 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 gql vulnerabilities disclosed?

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

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