VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

aiohasupervisor: vulnerability history, versions and safety

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

Vulert verdict on aiohasupervisor 0.8.1 i

Updated on 23 Oct 2026

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

Package health score 74/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 0.8.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2 i
  • Last release this month 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 aiohasupervisor, 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.8.1 22 Oct 2026 none Apache-2.0 — Details →
0.8.0 20 Oct 2026 none Apache-2.0 — Details →
0.7.0 09 Oct 2026 none Apache-2.0 — Details →
0.6.0 20 Jul 2026 none Apache-2.0 — Details →
0.5.0 02 Jun 2026 none Apache-2.0 — Details →
0.4.3 24 Mar 2026 none Apache-2.0 — Details →
0.4.2 17 Mar 2026 none Apache-2.0 — Details →
0.4.1 16 Mar 2026 none Apache-2.0 — Details →
0.4.0 13 Mar 2026 none Apache-2.0 — Details →
0.3.3 01 Oct 2025 none Apache-2.0 — Details →
0.3.3b0 23 Sep 2025 none Apache-2.0 — Details →
0.3.2 26 Aug 2025 none Apache-2.0 — Details →
0.3.2b0 19 Aug 2025 none Apache-2.0 — Details →
0.3.1 24 Apr 2025 none Apache-2.0 — Details →
0.3.1b1 11 Apr 2025 none Apache-2.0 — Details →
0.3.1b0 09 Apr 2025 none Apache-2.0 — Details →
0.3.0 05 Feb 2025 none Apache-2.0 — Details →
0.3.0b0 04 Feb 2025 none Apache-2.0 — Details →
0.2.2b6 28 Jan 2025 none Apache-2.0 — Details →
0.2.2b5 21 Dec 2024 none Apache-2.0 — Details →
0.2.2b4 20 Dec 2024 none Apache-2.0 — Details →
0.2.2b3 20 Dec 2024 none Apache-2.0 — Details →
0.2.2b2 17 Dec 2024 none Apache-2.0 — Details →
0.2.2b1 17 Dec 2024 none Apache-2.0 — Details →
0.2.2b0 09 Dec 2024 none Apache-2.0 — Details →
0.2.1 31 Oct 2024 none Apache-2.0 — Details →
0.2.0 28 Oct 2024 none Apache-2.0 — Details →
0.2.0b0 11 Oct 2024 none Apache-2.0 — Details →
0.1.0 26 Sep 2024 none Apache-2.0 — Details →
0.1.0b1 19 Sep 2024 none Apache-2.0 — Details →
0.1.0b0 30 Aug 2024 none Apache-2.0 — Details →

All 31 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 aiohasupervisor

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 aiohasupervisor

Is aiohasupervisor safe to use?

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

Vulert scores aiohasupervisor 74/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 aiohasupervisor affected?

No. 0.8.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.

How many vulnerabilities does aiohasupervisor have?

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

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

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