VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

dill: vulnerability history, versions and safety

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

Vulert verdict on dill 0.4.1 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 0.4.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 12,205 packages i
  • Stars 2,451 i
  • OpenSSF scorecard 3/10 i
  • Last release 9 months ago 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 dill, 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
0.4.1 19 Jan 2026 none BSD-3-Clause — Details →
0.4.0 16 Apr 2025 none BSD-3-Clause — Details →
0.3.9 29 Sep 2024 none BSD-3-Clause — Details →
0.3.8 27 Jan 2024 none BSD-3-Clause — Details →
0.3.7 22 Jul 2023 none BSD-3-Clause — Details →
0.3.6 23 Oct 2022 none BSD-3-Clause — Details →
0.3.5.1 20 May 2022 none BSD-3-Clause — Details →
0.3.5 19 May 2022 none BSD-3-Clause — Details →
0.3.4 13 Jun 2021 none BSD-3-Clause — Details →
0.3.3 02 Nov 2020 none BSD-3-Clause — Details →
0.3.2 15 Jun 2020 none BSD-3-Clause — Details →
0.3.1.1 28 Sep 2019 none — — Details →
0.3.0 26 Jun 2019 none — — Details →
0.2.9 21 Jan 2019 none — — Details →
0.2.8.2 22 Jun 2018 none — — Details →
0.2.8.1 21 Jun 2018 none — — Details →
0.2.8 21 Jun 2018 none — — Details →
0.2.7.1 18 Jul 2017 none — — Details →
0.2.7 06 Jul 2017 none — — Details →
0.2.6 01 Feb 2017 none BSD-3-Clause — Details →
0.2.5 06 Feb 2016 none non-standard — Details →
0.1.0a1 22 Dec 2015 none — — Details →
0.2.4 05 Aug 2015 none non-standard — Details →
0.2.3 22 Jun 2015 none non-standard — Details →
0.2.2 26 Dec 2014 none non-standard — Details →
0.2.1 01 Jun 2014 none non-standard — Details →
0.2.0 19 May 2014 none non-standard — Details →
0.2.0b1 27 Nov 2013 none — — Details →
0.2.0a1 20 Oct 2013 none — — Details →
0.2a1.win32 — none — — Details →
0.2b1.win32 — none — — Details →
0.3.1 — none — — Details →

All 32 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 dill

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 dill

Is dill safe to use?

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

Vulert scores dill 81/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 dill affected?

No. 0.4.1, 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 dill should I use?

0.4.1 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 dill have?

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

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

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