Vulnerability Database · PyPI · Package report

graphdatascience: vulnerability history, versions and safety

Q: How do I monitor graphdatascience for upcoming vulnerabilities?

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

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

0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all graphdatascience vulnerabilities

Vulert verdict on graphdatascience 2.2.0 i

Updated on 23 Oct 2026

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

Package health score 76/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Quiet

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

Current release 2.2.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 6 packages i
Stars 248 i
OpenSSF scorecard 5/10 i
Last release this month i
Licence Apache-2.0 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for graphdatascience, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
2.2.0	14 Oct 2026	none	Apache-2.0	—	Details →
2.1.0	28 Sep 2026	none	Apache-2.0	—	Details →
2.0.0	18 Sep 2026	none	Apache-2.0	—	Details →
2.0.0a6	10 Sep 2026	none	Apache-2.0	—	Details →
2.0.0a5	25 Aug 2026	none	Apache-2.0	—	Details →
2.0.0a4	13 Aug 2026	none	Apache-2.0	—	Details →
2.0.0a3	05 Aug 2026	none	Apache-2.0	—	Details →
2.0.0a2	31 Jul 2026	none	Apache-2.0	—	Details →
2.0.0a1	26 Jun 2026	none	Apache-2.0	—	Details →
1.22.0	04 Jun 2026	none	Apache-2.0	—	Details →
1.21.0	16 Apr 2026	none	Apache-2.0	—	Details →
1.21.0a2	16 Apr 2026	none	Apache-2.0	—	Details →
1.21.0a1	30 Mar 2026	none	Apache-2.0	—	Details →
1.20.0	26 Feb 2026	none	Apache-2.0	—	Details →
1.20.0a2	25 Feb 2026	none	Apache-2.0	—	Details →
1.20.0a1	04 Feb 2026	none	Apache-2.0	—	Details →
1.19.0	14 Jan 2026	none	Apache-2.0	—	Details →
1.19.0a1	19 Dec 2025	none	Apache-2.0	—	Details →
1.18.0	10 Dec 2025	none	Apache-2.0	—	Details →
1.18.0a1	17 Oct 2025	none	Apache-2.0	—	Details →
1.17.0	18 Sep 2025	none	Apache-2.0	—	Details →
1.17.0a1	25 Jul 2025	none	Apache-2.0	—	Details →
1.16.0	30 Jun 2025	none	Apache-2.0	—	Details →
1.15.1	19 May 2025	none	Apache-2.0	—	Details →
1.15.0	06 May 2025	none	Apache-2.0	—	Details →
1.15.0a2	10 Apr 2025	none	Apache-2.0	—	Details →
1.15.0a1	24 Mar 2025	none	Apache-2.0	—	Details →
1.14.0	20 Feb 2025	none	Apache-2.0	—	Details →
1.13.0	07 Jan 2025	none	Apache-2.0	—	Details →
1.12.0	08 Oct 2024	none	Apache-2.0	—	Details →
1.12.0a1	02 Sep 2024	none	Apache-2.0	—	Details →
1.11.0	31 Jul 2024	none	Apache-2.0	—	Details →
1.11.0a4	18 Jul 2024	none	Apache-2.0	—	Details →
1.11.0a3	05 Jul 2024	none	Apache-2.0	—	Details →
1.11.0a2	10 Jun 2024	none	Apache-2.0	—	Details →
1.11.0a1	28 May 2024	none	Apache-2.0	—	Details →
1.10.0	03 Apr 2024	none	Apache-2.0	—	Details →
1.10.0a1	27 Feb 2024	none	Apache-2.0	—	Details →
1.9.0	17 Jan 2024	none	Apache-2.0	—	Details →
1.8.0	10 Oct 2023	none	Apache-2.0	—	Details →
1.7.0	15 Jun 2023	none	Apache-2.0	—	Details →
1.7.0a1	24 May 2023	none	Apache-2.0	—	Details →
1.6.0	31 Jan 2023	none	Apache-2.0	—	Details →
1.6.0rc1	13 Jan 2023	none	Apache-2.0	—	Details →
1.5.0	02 Nov 2022	none	Apache-2.0	—	Details →
1.4.0	30 Sep 2022	none	Apache-2.0	—	Details →
1.3.0	23 Aug 2022	none	Apache-2.0	—	Details →
1.3.0a1	11 Aug 2022	none	Apache-2.0	—	Details →
1.2.0	05 Jul 2022	none	Apache-2.0	—	Details →
1.1.0	09 Jun 2022	none	Apache-2.0	—	Details →
1.1.0rc1	02 Jun 2022	none	Apache-2.0	—	Details →
1.1.0a2	19 May 2022	none	Apache-2.0	—	Details →
1.1.0a1	06 May 2022	none	Apache-2.0	—	Details →
1.0.0	24 Mar 2022	none	Apache-2.0	—	Details →
0.1.0	25 Feb 2022	none	Apache-2.0	—	Details →
0.0.9	03 Feb 2022	none	Apache-2.0	—	Details →
0.0.8	24 Jan 2022	none	Apache-2.0	—	Details →
0.0.7	20 Jan 2022	none	Apache-2.0	—	Details →

All 58 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for graphdatascience

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 graphdatascience

Is graphdatascience safe to use?

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

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

No. 2.2.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 graphdatascience should I use?

2.2.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 graphdatascience have?

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

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

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