VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sphinx-autoapi: vulnerability history, versions and safety

sphinx-autoapi 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 sphinx-autoapi vulnerabilities

Vulert verdict on sphinx-autoapi 3.8.1 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 3.8.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 57 packages i
  • Stars 496 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago 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 sphinx-autoapi, 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
3.8.1 23 Aug 2026 none MIT — Details →
3.8.0 08 Mar 2026 none MIT — Details →
3.7.0 11 Feb 2026 none MIT — Details →
3.6.1 06 Oct 2025 none MIT — Details →
3.6.0 18 Feb 2025 none MIT — Details →
3.5.0 10 Feb 2025 none MIT — Details →
3.4.0 30 Nov 2024 none MIT — Details →
3.3.3 26 Oct 2024 none MIT — Details →
3.3.2 25 Sep 2024 none MIT — Details →
3.3.1 02 Sep 2024 none MIT — Details →
3.3.0 29 Aug 2024 none MIT — Details →
3.2.1 23 Jul 2024 none MIT — Details →
3.2.0 20 Jul 2024 none MIT — Details →
3.1.2 20 Jun 2024 none MIT — Details →
3.1.1 23 May 2024 none MIT — Details →
3.1.0 20 May 2024 none MIT — Details →
3.1.0b0 12 Apr 2024 none MIT — Details →
3.0.0a4 24 Mar 2024 none MIT — Details →
3.1.0a3 16 Feb 2024 none MIT — Details →
3.1.0a2 16 Feb 2024 none MIT — Details →
3.1.0a1 01 Feb 2024 none MIT — Details →
3.0.0 26 Sep 2023 none MIT — Details →
2.1.1 10 Jun 2023 none MIT — Details →
2.1.0 28 Mar 2023 none MIT — Details →
2.0.1 17 Jan 2023 none MIT — Details →
2.0.0 28 Sep 2022 none MIT — Details →
1.9.0 25 Jul 2022 none MIT — Details →
1.8.4 16 Aug 2021 none MIT — Details →
1.8.3 01 Aug 2021 none MIT — Details →
1.8.2 27 Jul 2021 none MIT — Details →
1.8.1 25 Apr 2021 none MIT — Details →
1.8.0 13 Apr 2021 none MIT — Details →
1.7.0 01 Feb 2021 none non-standard — Details →
1.6.0 20 Jan 2021 none non-standard — Details →
1.5.1 03 Oct 2020 none non-standard — Details →
1.5.0 01 Sep 2020 none non-standard — Details →
1.4.0 08 Jun 2020 none non-standard — Details →
1.3.0 06 Apr 2020 none non-standard — Details →
1.2.1 10 Oct 2019 none non-standard — Details →
1.2.0 06 Oct 2019 none non-standard — Details →
1.1.0 23 Jun 2019 none non-standard — Details →
1.0.0 24 Apr 2019 none non-standard — Details →
0.7.1 05 Feb 2019 none non-standard — Details →
0.7.0 31 Jan 2019 none non-standard — Details →
0.6.2 15 Nov 2018 none non-standard — Details →
0.6.1 15 Nov 2018 none non-standard — Details →
0.6.0 20 Aug 2018 none non-standard — Details →
0.5.0 13 Nov 2017 none non-standard — Details →
0.4.0 18 Nov 2015 none non-standard — Details →
0.3.0 12 Oct 2015 none non-standard — Details →
0.2.0 05 Sep 2015 none non-standard — Details →

All 51 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 sphinx-autoapi

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 sphinx-autoapi

Is sphinx-autoapi safe to use?

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

Vulert scores sphinx-autoapi 78/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 sphinx-autoapi affected?

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

Which version of sphinx-autoapi should I use?

3.8.1 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 sphinx-autoapi have?

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

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

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