VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pygraphviz: vulnerability history, versions and safety

pygraphviz 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 pygraphviz vulnerabilities

Vulert verdict on pygraphviz 2.0.4 i

Updated on 23 Oct 2026

Good news: 2.0.4, 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 2.0.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.0.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 220 packages i
  • Stars 848 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 pygraphviz, 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.0.4 15 Oct 2026 none BSD-3-Clause — Details →
2.0.3 01 Oct 2026 none BSD-3-Clause — Details →
2.0.2 16 Sep 2026 none BSD-3-Clause — Details →
2.0.2rc1 14 Sep 2026 none BSD-3-Clause — Details →
2.0.1 20 Jul 2026 none BSD-3-Clause — Details →
2.0.0 25 Jun 2026 none BSD-3-Clause — Details →
2.0.0rc4 20 Jun 2026 none BSD-3-Clause — Details →
2.0.0rc3 18 Jun 2026 none BSD-3-Clause — Details →
2.0.0rc2 13 Jun 2026 none BSD-3-Clause — Details →
2.0.0rc1 07 Jun 2026 none BSD-3-Clause — Details →
2.0.0rc0 07 Jun 2026 none BSD-3-Clause — Details →
1.14.0 29 Sep 2024 none BSD-3-Clause — Details →
1.14.0rc0 29 Sep 2024 none BSD-3-Clause — Details →
1.13.0 09 May 2024 none BSD-3-Clause — Details →
1.13.0rc0 09 May 2024 none BSD-3-Clause — Details →
1.12.0 08 Jan 2024 none BSD-3-Clause — Details →
1.12.0rc3 08 Jan 2024 none BSD-3-Clause — Details →
1.11.0 01 Jun 2023 none non-standard — Details →
1.11.0rc1 31 May 2023 none non-standard — Details →
1.10.0 19 Aug 2022 none non-standard — Details →
1.10.0rc1 17 Aug 2022 none non-standard — Details →
1.9.0 09 Feb 2022 none non-standard — Details →
1.8.0 20 Jan 2022 none non-standard — Details →
1.8.0rc1 15 Jan 2022 none non-standard — Details →
1.7.0 01 Feb 2021 none non-standard — Details →
1.7.0rc2 24 Jan 2021 none non-standard — Details →
1.7.0rc1 04 Jan 2021 none non-standard — Details →
1.6.0 06 Aug 2020 none non-standard — Details →
1.6.0rc1 05 Aug 2020 none non-standard — Details →
1.5.0 10 Sep 2018 none non-standard — Details →
1.4.0rc1 06 Nov 2016 none non-standard — Details →
1.3.1 06 Sep 2015 none non-standard — Details →
1.3.0 05 Sep 2015 none non-standard — Details →
1.3.0rc2 11 Oct 2014 none non-standard — Details →
1.3.0rc1 21 Sep 2014 none non-standard — Details →
1.2.0 03 Aug 2013 none non-standard — Details →
1.1.0 14 May 2011 none non-standard — Details →
1.1.0rc1 12 Feb 2011 none non-standard — Details →
1.0.0 01 Aug 2010 none non-standard — Details →
1.0.0rc6 31 Jul 2010 none non-standard — Details →
1.0.0rc5 30 Jul 2010 none non-standard — Details →
1.0.0rc4 28 Jul 2010 none non-standard — Details →
1.0.0rc3 27 Jul 2010 none non-standard — Details →
1.0.0rc2 24 Jul 2010 none non-standard — Details →
1.0.0rc1 24 Jul 2010 none non-standard — Details →
0.99.1 07 Dec 2008 none non-standard — Details →
0.99.0 18 Nov 2008 none non-standard — Details →
0.37.0 17 Aug 2008 none non-standard — Details →
0.36.0 13 Jan 2008 none non-standard — Details →
0.35.0 23 Jul 2007 none non-standard — Details →
0.34.0 12 Apr 2007 none non-standard — Details →
0.99-py2.4-linux-i686 — none — — Details →
0.99-py2.5-linux-i686 — none — — Details →
0.99.1-py2.4-linux-i686 — none — — Details →
0.99.1-py2.5-linux-i686 — none — — 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 pygraphviz

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 pygraphviz

Is pygraphviz safe to use?

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

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

No. 2.0.4, 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 pygraphviz should I use?

2.0.4 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 pygraphviz have?

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

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

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