Vulnerability Database · PyPI · Package report
py2neo: vulnerability history, versions and safety
py2neo is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the PyPI ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on py2neo 2021.2.4 i
Updated on 23 Oct 2026
Good news: 2021.2.4, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Quiet
What to do: Stay on 2021.2.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 2021.2.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2021.2.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 76 packages i
- Stars 1,190 i
- OpenSSF scorecard 2/10 i
- Last release 36 months ago 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.
01 Versions
Which versions are affected
Every version Vulert tracks for py2neo, 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.
- 2021.2.4 20 Oct 2023
All 1 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 py2neo
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
Questions
About py2neo
Is py2neo safe to use?
Vulert has no vulnerabilities on record for py2neo 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 py2neo's Vulert package health score?
Vulert scores py2neo 62/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 py2neo affected?
No. 2021.2.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 py2neo should I use?
2021.2.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 py2neo have?
0 vulnerabilities are recorded for py2neo 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 py2neo vulnerabilities disclosed?
0 vulnerabilities were recorded for py2neo 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 py2neo 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 py2neo for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the py2neo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.