VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

types-aiofiles: vulnerability history, versions and safety

types-aiofiles 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 types-aiofiles vulnerabilities

Vulert verdict on types-aiofiles 25.1.0.20260518 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 25.1.0.20260518 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 133 packages i
  • Stars 5,136 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 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 types-aiofiles, 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
25.1.0.20260518 18 May 2026 none Apache-2.0 — Details →
25.1.0.20260508 08 May 2026 none Apache-2.0 — Details →
25.1.0.20260409 09 Apr 2026 none Apache-2.0 — Details →
25.1.0.20260408 08 Apr 2026 none Apache-2.0 — Details →
25.1.0.20251011 11 Oct 2025 none Apache-2.0 — Details →
24.1.0.20250822 22 Aug 2025 none Apache-2.0 — Details →
24.1.0.20250809 09 Aug 2025 none Apache-2.0 — Details →
24.1.0.20250801 01 Aug 2025 none Apache-2.0 — Details →
24.1.0.20250708 08 Jul 2025 none Apache-2.0 — Details →
24.1.0.20250606 06 Jun 2025 none Apache-2.0 — Details →
24.1.0.20250516 16 May 2025 none Apache-2.0 — Details →
24.1.0.20250326 26 Mar 2025 none Apache-2.0 — Details →
24.1.0.20241221 21 Dec 2024 none Apache-2.0 — Details →
24.1.0.20240626 26 Jun 2024 none Apache-2.0 — Details →
23.2.0.20240623 23 Jun 2024 none Apache-2.0 — Details →
23.2.0.20240403 03 Apr 2024 none Apache-2.0 — Details →
23.2.0.20240331 31 Mar 2024 none Apache-2.0 — Details →
23.2.0.20240311 11 Mar 2024 none Apache-2.0 — Details →
23.2.0.20240310 10 Mar 2024 none Apache-2.0 — Details →
23.2.0.20240106 06 Jan 2024 none Apache-2.0 — Details →
23.2.0.0 16 Aug 2023 none Apache-2.0 — Details →
23.1.0.5 20 Jul 2023 none Apache-2.0 — Details →
23.1.0.4 07 Jun 2023 none Apache-2.0 — Details →
23.1.0.3 22 May 2023 none Apache-2.0 — Details →
23.1.0.2 29 Apr 2023 none Apache-2.0 — Details →
23.1.0.1 27 Mar 2023 none Apache-2.0 — Details →
23.1.0.0 09 Mar 2023 none Apache-2.0 — Details →
22.1.0.9 21 Feb 2023 none Apache-2.0 — Details →
22.1.0.8 15 Feb 2023 none Apache-2.0 — Details →
22.1.0.7 09 Feb 2023 none Apache-2.0 — Details →
22.1.0.6 18 Jan 2023 none Apache-2.0 — Details →
22.1.0.5 18 Jan 2023 none Apache-2.0 — Details →
22.1.0.4 26 Nov 2022 none Apache-2.0 — Details →
22.1.0.3 13 Nov 2022 none Apache-2.0 — Details →
22.1.0.2 08 Nov 2022 none Apache-2.0 — Details →
22.1.0.1 05 Nov 2022 none Apache-2.0 — Details →
22.1.0 09 Sep 2022 none Apache-2.0 — Details →
0.8.11 29 Aug 2022 none Apache-2.0 — Details →
0.8.10 18 Jul 2022 none Apache-2.0 — Details →
0.8.9 06 Jul 2022 none Apache-2.0 — Details →
0.8.8 16 Apr 2022 none Apache-2.0 — Details →
0.8.7 16 Apr 2022 none Apache-2.0 — Details →
0.8.6 29 Mar 2022 none Apache-2.0 — Details →
0.8.5 16 Mar 2022 none Apache-2.0 — Details →
0.8.4 07 Mar 2022 none Apache-2.0 — Details →
0.8.3 13 Jan 2022 none Apache-2.0 — Details →
0.8.2 08 Jan 2022 none Apache-2.0 — Details →
0.8.1 07 Jan 2022 none Apache-2.0 — Details →
0.8.0 02 Jan 2022 none Apache-2.0 — Details →
0.7.3 28 Dec 2021 none Apache-2.0 — Details →
0.7.2 26 Dec 2021 none Apache-2.0 — Details →
0.7.1 25 Dec 2021 none Apache-2.0 — Details →
0.7.0 12 Oct 2021 none Apache-2.0 — Details →
0.1.9 08 Aug 2021 none Apache-2.0 — Details →
0.1.8 08 Aug 2021 none Apache-2.0 — Details →
0.1.7 11 Jul 2021 none Apache-2.0 — Details →
0.1.6 06 Jul 2021 none Apache-2.0 — Details →
0.1.5 17 Jun 2021 none Apache-2.0 — Details →
0.1.4 13 Jun 2021 none Apache-2.0 — Details →
0.1.3 17 May 2021 none Apache-2.0 — Details →
0.1.2 21 Apr 2021 none — — Details →
0.1.1 28 Feb 2021 none — — Details →
0.1.0 02 Feb 2021 none — — Details →

All 63 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 types-aiofiles

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 types-aiofiles

Is types-aiofiles safe to use?

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

Vulert scores types-aiofiles 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 types-aiofiles affected?

No. 25.1.0.20260518, 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 types-aiofiles should I use?

25.1.0.20260518 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 types-aiofiles have?

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

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

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