VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

platformdirs: vulnerability history, versions and safety

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

Vulert verdict on platformdirs 4.13.5 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.13.5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 54,935 packages i
  • Stars 993 i
  • Last release this month 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 platformdirs, 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
4.13.5 19 Oct 2026 none MIT — Details →
4.13.4 17 Oct 2026 none MIT — Details →
4.13.3 16 Oct 2026 none MIT — Details →
4.13.2 16 Oct 2026 none MIT — Details →
4.13.1 15 Oct 2026 none MIT — Details →
4.13.0 11 Oct 2026 none MIT — Details →
4.12.4 07 Oct 2026 none MIT — Details →
4.12.3 03 Oct 2026 none MIT — Details →
4.12.2 29 Sep 2026 none MIT — Details →
4.12.1 28 Sep 2026 none MIT — Details →
4.12.0 26 Sep 2026 none MIT — Details →
4.11.15 26 Sep 2026 none MIT — Details →
4.11.14 25 Sep 2026 none MIT — Details →
4.11.13 25 Sep 2026 none MIT — Details →
4.11.12 22 Sep 2026 none MIT — Details →
4.11.11 19 Sep 2026 none MIT — Details →
4.11.10 18 Sep 2026 none MIT — Details →
4.11.9 16 Sep 2026 none MIT — Details →
4.11.8 08 Sep 2026 none MIT — Details →
4.11.7 01 Sep 2026 none MIT — Details →
4.11.6 01 Sep 2026 none MIT — Details →
4.11.5 27 Aug 2026 none MIT — Details →
4.11.4 24 Aug 2026 none MIT — Details →
4.11.3 13 Aug 2026 none MIT — Details →
4.11.2 10 Aug 2026 none MIT — Details →
4.11.1 07 Aug 2026 none MIT — Details →
4.11.0 21 Jul 2026 none MIT — Details →
4.10.1 18 Jul 2026 none MIT — Details →
4.10.0 28 May 2026 none MIT — Details →
4.9.6 09 Apr 2026 none MIT — Details →
4.9.4 05 Mar 2026 none MIT — Details →
4.9.2 16 Feb 2026 none MIT — Details →
4.9.1 14 Feb 2026 none MIT — Details →
4.9.0 14 Feb 2026 none MIT — Details →
4.8.0 14 Feb 2026 none MIT — Details →
4.7.1 13 Feb 2026 none MIT — Details →
4.7.0 12 Feb 2026 none MIT — Details →
4.6.0 12 Feb 2026 none MIT — Details →
4.5.1 05 Dec 2025 none MIT — Details →
4.5.0 08 Oct 2025 none MIT — Details →
4.4.0 26 Aug 2025 none MIT — Details →
4.3.8 07 May 2025 none MIT — Details →
4.3.7 19 Mar 2025 none MIT — Details →
4.3.6 17 Sep 2024 none MIT — Details →
4.3.5 17 Sep 2024 none MIT — Details →
4.3.4 17 Sep 2024 none MIT — Details →
4.3.3 13 Sep 2024 none MIT — Details →
4.3.2 08 Sep 2024 none MIT — Details →
4.3.1 07 Sep 2024 none MIT — Details →
4.3.0 07 Sep 2024 none MIT — Details →
4.2.2 15 May 2024 none MIT — Details →
4.2.1 23 Apr 2024 none MIT — Details →
4.2.0 31 Jan 2024 none MIT — Details →
4.1.0 04 Dec 2023 none MIT — Details →
4.0.0 10 Nov 2023 none MIT — Details →
3.11.0 02 Oct 2023 none MIT — Details →
3.10.0 29 Jul 2023 none MIT — Details →
3.9.1 15 Jul 2023 none MIT — Details →
3.9.0 15 Jul 2023 none MIT — Details →
3.8.1 06 Jul 2023 none MIT — Details →
3.8.0 23 Jun 2023 none MIT — Details →
3.7.0 21 Jun 2023 none MIT — Details →
3.6.0 18 Jun 2023 none MIT — Details →
3.5.3 10 Jun 2023 none MIT — Details →
3.5.2 10 Jun 2023 none MIT — Details →
3.5.1 11 May 2023 none MIT — Details →
3.5.0 27 Apr 2023 none MIT — Details →
3.4.0 26 Apr 2023 none MIT — Details →
3.3.0 25 Apr 2023 none MIT — Details →
3.2.0 25 Mar 2023 none MIT — Details →
3.1.1 10 Mar 2023 none MIT — Details →
3.1.0 03 Mar 2023 none MIT — Details →
3.0.0 06 Feb 2023 none MIT — Details →
2.6.2 28 Dec 2022 none MIT — Details →
2.6.1 28 Dec 2022 none MIT — Details →
2.6.0 07 Dec 2022 none MIT — Details →
2.5.4 13 Nov 2022 none MIT — Details →
2.5.3 06 Nov 2022 none non-standard — Details →
2.5.2 18 Apr 2022 none MIT — Details →
2.5.1 19 Feb 2022 none MIT — Details →
2.5.0 09 Feb 2022 none MIT — Details →
2.4.1 26 Dec 2021 none MIT — Details →
2.4.0 25 Sep 2021 none MIT — Details →
2.3.0 30 Aug 2021 none MIT — Details →
2.2.0 29 Jul 2021 none MIT — Details →
2.1.0 25 Jul 2021 none MIT — Details →
2.0.2 13 Jul 2021 none MIT — Details →
2.0.0 12 Jul 2021 none MIT — Details →
2.0.0a3 14 May 2021 none MIT — Details →
2.0.0a2 13 May 2021 none MIT — Details →
2.0.0a1 13 May 2021 none MIT — Details →

All 91 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 platformdirs

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 platformdirs

Is platformdirs safe to use?

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

Vulert scores platformdirs 93/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 platformdirs affected?

No. 4.13.5, 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.

How many vulnerabilities does platformdirs have?

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

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

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