VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sphinx-autobuild: vulnerability history, versions and safety

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

Vulert verdict on sphinx-autobuild 2025.8.25 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

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

  • Current release 2025.8.25 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 91 packages i
  • Stars 611 i
  • Last release 13 months 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-autobuild, 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
2025.8.25 25 Aug 2025 none MIT — Details →
2024.10.3 02 Oct 2024 none MIT — Details →
2024.10.2 02 Oct 2024 none MIT — Details →
2024.9.19 18 Sep 2024 none MIT — Details →
2024.9.18 18 Sep 2024 none MIT — Details →
2024.9.17 17 Sep 2024 none MIT — Details →
2024.9.3 03 Sep 2024 none MIT — Details →
2024.4.16 16 Apr 2024 none MIT — Details →
2024.4.13 13 Apr 2024 none MIT — Details →
2024.2.4 04 Feb 2024 none MIT — Details →
2021.3.14 14 Mar 2021 none MIT — Details →
2020.9.1 31 Aug 2020 none MIT — Details →
0.7.1 05 Jul 2017 none MIT — Details →
0.7.0 05 Jul 2017 none MIT — Details →
0.6.0 13 Feb 2016 none MIT — Details →
0.5.2 10 Apr 2015 none MIT — Details →
0.5.1 10 Apr 2015 none MIT — Details →
0.5.0 28 Jan 2015 none MIT — Details →
0.4.0 23 Dec 2014 none MIT — Details →
0.3.0 21 Aug 2014 none MIT — Details →
0.2.3 25 Dec 2013 none MIT — Details →
0.2.2 25 Dec 2013 none MIT — Details →
0.2.1 25 Dec 2013 none MIT — Details →
0.2.0 25 Dec 2013 none MIT — Details →
0.1.0 25 Dec 2013 none MIT — Details →

All 25 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-autobuild

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-autobuild

Is sphinx-autobuild safe to use?

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

Vulert scores sphinx-autobuild 80/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-autobuild affected?

No. 2025.8.25, 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-autobuild should I use?

2025.8.25 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-autobuild have?

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

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

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