VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

packaging: vulnerability history, versions and safety

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

Vulert verdict on packaging 26.3.0 i

Updated on 23 Oct 2026

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

Package health score 90/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 26.3.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 167,029 packages i
  • Stars 752 i
  • OpenSSF scorecard 7/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 OR BSD-2-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 packaging, 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
26.3.0 04 Aug 2026 none Apache-2.0 OR BSD-2-Clause — Details →
26.2.0 24 Apr 2026 none Apache-2.0 OR BSD-2-Clause — Details →
26.1.0 14 Apr 2026 none Apache-2.0 OR BSD-2-Clause — Details →
26.0.0 21 Jan 2026 none Apache-2.0 OR BSD-2-Clause — Details →
26.0.0rc3 15 Jan 2026 none Apache-2.0 OR BSD-2-Clause — Details →
26.0.0rc2 12 Jan 2026 none Apache-2.0 OR BSD-2-Clause — Details →
26.0.0rc1 09 Jan 2026 none Apache-2.0 OR BSD-2-Clause — Details →
25.0.0 19 Apr 2025 none non-standard — Details →
24.2.0 08 Nov 2024 none non-standard — Details →
24.1.0 09 Jun 2024 none non-standard — Details →
24.0.0 10 Mar 2024 none non-standard — Details →
23.2.0 01 Oct 2023 none non-standard — Details →
23.1.0 12 Apr 2023 none non-standard — Details →
23.0.0 08 Jan 2023 none non-standard — Details →
22.0.0 07 Dec 2022 none non-standard — Details →
21.3.0 18 Nov 2021 none Apache-2.0 OR BSD-2-Clause — Details →
21.2.0 29 Oct 2021 none Apache-2.0 OR BSD-2-Clause — Details →
21.1.0 29 Oct 2021 none Apache-2.0 OR BSD-2-Clause — Details →
21.0.0 03 Jul 2021 none Apache-2.0 OR BSD-2-Clause — Details →
20.9.0 29 Jan 2021 none Apache-2.0 OR BSD-2-Clause — Details →
20.8.0 12 Dec 2020 none Apache-2.0 OR BSD-2-Clause — Details →
20.7.0 28 Nov 2020 none non-standard — Details →
20.6.0 28 Nov 2020 none non-standard — Details →
20.5.0 27 Nov 2020 none non-standard — Details →
20.4.0 19 May 2020 none Apache-2.0 OR BSD-2-Clause — Details →
20.3.0 05 Mar 2020 none non-standard — Details →
20.2.0 05 Mar 2020 none non-standard — Details →
20.1.0 24 Jan 2020 none non-standard — Details →
20.0.0 06 Jan 2020 none non-standard — Details →
19.2.0 18 Sep 2019 none non-standard — Details →
19.1.0 30 Jul 2019 none non-standard — Details →
19.0.0 20 Jan 2019 none non-standard — Details →
18.0.0 26 Sep 2018 none non-standard — Details →
17.1.0 28 Feb 2018 none non-standard — Details →
17.0.0 28 Feb 2018 none non-standard — Details →
16.8.0 29 Oct 2016 none non-standard — Details →
16.7.0 23 Apr 2016 none non-standard — Details →
16.6.0 29 Mar 2016 none non-standard — Details →
16.5.0 26 Feb 2016 none non-standard — Details →
16.4.0 23 Feb 2016 none non-standard — Details →
16.3.0 22 Feb 2016 none non-standard — Details →
16.2.0 09 Feb 2016 none non-standard — Details →
16.1.0 08 Feb 2016 none non-standard — Details →
16.0.0 19 Jan 2016 none non-standard — Details →
15.3.0 02 Aug 2015 none Apache-2.0 — Details →
15.2.0 13 May 2015 none Apache-2.0 — Details →
15.1.0 15 Apr 2015 none Apache-2.0 — Details →
15.0.0 03 Jan 2015 none Apache-2.0 — Details →
14.5.0 18 Dec 2014 none Apache-2.0 — Details →
14.4.0 15 Dec 2014 none Apache-2.0 — Details →
14.3.0 20 Nov 2014 none Apache-2.0 — Details →
14.2.0 10 Sep 2014 none Apache-2.0 — Details →
14.1.0 09 Sep 2014 none Apache-2.0 — Details →
14.0.0 05 Sep 2014 none Apache-2.0 — 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.

03 Vulnerabilities

Recorded vulnerabilities for packaging

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 packaging

Is packaging safe to use?

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

Vulert scores packaging 90/100, which reads as healthy. 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 packaging affected?

No. 26.3.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 packaging should I use?

26.3.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 packaging have?

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

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

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