VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

autogen-ext: vulnerability history, versions and safety

autogen-ext 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 autogen-ext vulnerabilities

Vulert verdict on autogen-ext 0.7.5 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.7.5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 42 packages i
  • Stars 61,441 i
  • OpenSSF scorecard 5/10 i
  • Last release 12 months ago i
  • Licence non-standard 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 autogen-ext, 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.7.5 30 Sep 2025 none non-standard — Details →
0.7.4 19 Aug 2025 none non-standard — Details →
0.7.3 19 Aug 2025 none non-standard — Details →
0.7.2 07 Aug 2025 none non-standard — Details →
0.7.1 28 Jul 2025 none non-standard — Details →
0.7.0 28 Jul 2025 none non-standard — Details →
0.6.4 09 Jul 2025 none non-standard — Details →
0.6.3 09 Jul 2025 none non-standard — Details →
0.6.2 30 Jun 2025 none non-standard — Details →
0.6.1 05 Jun 2025 none non-standard — Details →
0.6.0 05 Jun 2025 none non-standard — Details →
0.5.7 14 May 2025 none non-standard — Details →
0.5.6 02 May 2025 none non-standard — Details →
0.5.5 25 Apr 2025 none non-standard — Details →
0.5.4 22 Apr 2025 none non-standard — Details →
0.5.3 17 Apr 2025 none non-standard — Details →
0.5.2 15 Apr 2025 none non-standard — Details →
0.5.1 03 Apr 2025 none non-standard — Details →
0.5.0 03 Apr 2025 none non-standard — Details →
0.4.9.3 29 Mar 2025 none non-standard — Details →
0.4.9.2 14 Mar 2025 none non-standard — Details →
0.4.9.1 14 Mar 2025 none non-standard — Details →
0.4.9 12 Mar 2025 none non-standard — Details →
0.4.8.2 07 Mar 2025 none non-standard — Details →
0.4.8.1 05 Mar 2025 none non-standard — Details →
0.4.8 04 Mar 2025 none non-standard — Details →
0.4.7 15 Feb 2025 none non-standard — Details →
0.4.6 11 Feb 2025 none non-standard — Details →
0.4.5 01 Feb 2025 none non-standard — Details →
0.4.4 28 Jan 2025 none non-standard — Details →
0.4.3 21 Jan 2025 none non-standard — Details →
0.4.2 15 Jan 2025 none non-standard — Details →
0.4.1 13 Jan 2025 none non-standard — Details →
0.4.0 09 Jan 2025 none non-standard — Details →
0.4.0.dev13 30 Dec 2024 none non-standard — Details →
0.4.0.dev12 27 Dec 2024 none non-standard — Details →
0.4.0.dev11 10 Dec 2024 none non-standard — Details →
0.4.0.dev10 10 Dec 2024 none non-standard — Details →
0.4.0.dev9 06 Dec 2024 none non-standard — Details →
0.4.0.dev8 27 Nov 2024 none non-standard — Details →
0.4.0.dev7 25 Nov 2024 none non-standard — Details →
0.4.0.dev6 11 Nov 2024 none non-standard — Details →
0.4.0.dev5 11 Nov 2024 none non-standard — Details →
0.4.0.dev4 06 Nov 2024 none non-standard — Details →
0.4.0.dev3 01 Nov 2024 none non-standard — Details →
0.4.0.dev2 23 Oct 2024 none non-standard — Details →
0.4.0.dev1 14 Oct 2024 none non-standard — Details →
0.4.0.dev0 09 Oct 2024 none non-standard — Details →
0.0.1 28 Aug 2024 none MIT — Details →

All 49 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 autogen-ext

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 autogen-ext

Is autogen-ext safe to use?

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

Vulert scores autogen-ext 82/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 autogen-ext affected?

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

Which version of autogen-ext should I use?

0.7.5 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 autogen-ext have?

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

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

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