Vulnerability Database · PyPI · Package report
dpath: vulnerability history, versions and safety
dpath 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 dpath 2.2.0 i
Updated on 23 Oct 2026
Good news: 2.2.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Slowing
- Popularity Widely used
- 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 748 packages i
- Stars 628 i
- Last release 28 months ago 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 dpath, 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.
- 2.2.0 12 Jun 2024
- 2.1.6 21 May 2023
- 2.1.5 25 Mar 2023
- 2.1.4 09 Jan 2023
- 2.1.3 13 Dec 2022
- 2.1.2 05 Dec 2022
- 2.1.1 30 Nov 2022
- 2.1.0 27 Nov 2022
- 2.0.8 23 Nov 2022
- 2.0.7 22 Nov 2022
- 2.0.6 01 Feb 2022
- 2.0.5 12 Sep 2021
- 2.0.4 11 Sep 2021
- 2.0.3 08 Sep 2021
- 2.0.2 02 Sep 2021
- 2.0.1 26 Jan 2020
- 2.0.0 26 Jan 2020
- 1.5.0 28 Dec 2019
- 1.4.2 13 Jan 2018
- 1.4.0 12 Jun 2015
- 1.3.3 25 Apr 2015
- 1.3.2 31 Jan 2015
- 1.3.0.post1 01 Jan 2015
- 1.2.0.post70 01 Apr 2014
- 1.2.0.post68 01 Apr 2014
- 1.2.0.post67 01 Apr 2014
- 1.2.0.post62 01 Apr 2014
- 1.2.0.post61 01 Apr 2014
- 1.2.0.post60 01 Apr 2014
- 1.2.0.post59 01 Apr 2014
- 1.2.0.post58 01 Apr 2014
- 1.2.0.post57 01 Apr 2014
- 1.2.0.post56 01 Apr 2014
- 1.2.0.post55 01 Apr 2014
- 1.2.0.post54 01 Apr 2014
- 1.2.0.post53 01 Apr 2014
- 1.2.0.post52 01 Apr 2014
- 1.2.0.post51 03 Feb 2014
- 1.2.0.post50 03 Feb 2014
- 1.2.0.post1 03 Feb 2014
- 1.2.0.post49 03 Feb 2014
- 1.2.0.post48 03 Feb 2014
- 1.2.0.post47 03 Feb 2014
- 1.2.0.post46 27 Jan 2014
- 1.2.0.post45 05 Oct 2013
- git-unknown 05 Oct 2013
- 1.2.0.post42 26 Sep 2013
- 1.2.0.post39 12 Jun 2013
- 1.2.0.post38 10 Jun 2013
- 1.2.0.post37 30 May 2013
- 1.1.0.post36 14 May 2013
- 1.1.0.post35 13 May 2013
- 1.1.0.post32 11 May 2013
- 1.1.0.post31 11 May 2013
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 2.2.0 | 12 Jun 2024 | none | MIT | — | Details → |
| 2.1.6 | 21 May 2023 | none | MIT | — | Details → |
| 2.1.5 | 25 Mar 2023 | none | MIT | — | Details → |
| 2.1.4 | 09 Jan 2023 | none | MIT | — | Details → |
| 2.1.3 | 13 Dec 2022 | none | MIT | — | Details → |
| 2.1.2 | 05 Dec 2022 | none | MIT | — | Details → |
| 2.1.1 | 30 Nov 2022 | none | MIT | — | Details → |
| 2.1.0 | 27 Nov 2022 | none | MIT | — | Details → |
| 2.0.8 | 23 Nov 2022 | none | MIT | — | Details → |
| 2.0.7 | 22 Nov 2022 | none | MIT | — | Details → |
| 2.0.6 | 01 Feb 2022 | none | MIT | — | Details → |
| 2.0.5 | 12 Sep 2021 | none | MIT | — | Details → |
| 2.0.4 | 11 Sep 2021 | none | MIT | — | Details → |
| 2.0.3 | 08 Sep 2021 | none | MIT | — | Details → |
| 2.0.2 | 02 Sep 2021 | none | MIT | — | Details → |
| 2.0.1 | 26 Jan 2020 | none | MIT | — | Details → |
| 2.0.0 | 26 Jan 2020 | none | MIT | — | Details → |
| 1.5.0 | 28 Dec 2019 | none | MIT | — | Details → |
| 1.4.2 | 13 Jan 2018 | none | MIT | — | Details → |
| 1.4.0 | 12 Jun 2015 | none | MIT | — | Details → |
| 1.3.3 | 25 Apr 2015 | none | MIT | — | Details → |
| 1.3.2 | 31 Jan 2015 | none | MIT | — | Details → |
| 1.3.0.post1 | 01 Jan 2015 | none | MIT | — | Details → |
| 1.2.0.post70 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post68 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post67 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post62 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post61 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post60 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post59 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post58 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post57 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post56 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post55 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post54 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post53 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post52 | 01 Apr 2014 | none | MIT | — | Details → |
| 1.2.0.post51 | 03 Feb 2014 | none | MIT | — | Details → |
| 1.2.0.post50 | 03 Feb 2014 | none | MIT | — | Details → |
| 1.2.0.post1 | 03 Feb 2014 | none | MIT | — | Details → |
| 1.2.0.post49 | 03 Feb 2014 | none | MIT | — | Details → |
| 1.2.0.post48 | 03 Feb 2014 | none | MIT | — | Details → |
| 1.2.0.post47 | 03 Feb 2014 | none | MIT | — | Details → |
| 1.2.0.post46 | 27 Jan 2014 | none | MIT | — | Details → |
| 1.2.0.post45 | 05 Oct 2013 | none | MIT | — | Details → |
| git-unknown | 05 Oct 2013 | none | MIT | — | Details → |
| 1.2.0.post42 | 26 Sep 2013 | none | MIT | — | Details → |
| 1.2.0.post39 | 12 Jun 2013 | none | MIT | — | Details → |
| 1.2.0.post38 | 10 Jun 2013 | none | MIT | — | Details → |
| 1.2.0.post37 | 30 May 2013 | none | MIT | — | Details → |
| 1.1.0.post36 | 14 May 2013 | none | MIT | — | Details → |
| 1.1.0.post35 | 13 May 2013 | none | MIT | — | Details → |
| 1.1.0.post32 | 11 May 2013 | none | MIT | — | Details → |
| 1.1.0.post31 | 11 May 2013 | none | MIT | — | Details → |
All 54 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 dpath
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 dpath
Is dpath safe to use?
Vulert has no vulnerabilities on record for dpath 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 dpath's Vulert package health score?
Vulert scores dpath 73/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 dpath 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 dpath 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 dpath have?
0 vulnerabilities are recorded for dpath 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 dpath vulnerabilities disclosed?
0 vulnerabilities were recorded for dpath 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 dpath 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 dpath for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dpath version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.