Vulnerability Database · PyPI · Package report

library: vulnerability history, versions and safety

library 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.

Vulert verdict on library 4.0.0 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release 4.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 485 i
  • Last release this month i
  • Licence BSD-3-Clause 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 library, 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
4.0.0 19 Oct 2026 none BSD-3-Clause — Details →
3.2.11 11 Oct 2026 none non-standard — Details →
3.2.7 29 Sep 2026 none non-standard — Details →
3.2.6 10 Sep 2026 none non-standard — Details →
3.2.5 28 Aug 2026 none non-standard — Details →
3.2.4 22 Aug 2026 none non-standard — Details →
3.2.3 19 Aug 2026 none non-standard — Details →
3.2.2 16 Aug 2026 none non-standard — Details →
3.1.1 13 Jul 2026 none non-standard — Details →
3.0.175 13 Jul 2026 none non-standard — Details →
3.0.171 23 Jun 2026 none non-standard — Details →
3.0.170 04 Jun 2026 none non-standard — Details →
3.0.169 25 May 2026 none non-standard — Details →
3.0.167 05 Mar 2026 none non-standard — Details →
3.0.166 05 Mar 2026 none non-standard — Details →
3.0.165 24 Feb 2026 none non-standard — Details →
3.0.163 26 Jan 2026 none non-standard — Details →
3.0.160 05 Jan 2026 none non-standard — Details →
3.0.159 03 Jan 2026 none non-standard — Details →
3.0.158 29 Dec 2025 none non-standard — Details →
3.0.154 12 Dec 2025 none non-standard — Details →
3.0.151 26 Nov 2025 none non-standard — Details →
3.0.150 19 Nov 2025 none non-standard — Details →
3.0.148 10 Nov 2025 none non-standard — Details →
3.0.147 09 Nov 2025 none non-standard — Details →
3.0.142 05 Nov 2025 none non-standard — Details →
3.0.141 04 Nov 2025 none non-standard — Details →
3.0.140 03 Nov 2025 none non-standard — Details →
3.0.138 02 Nov 2025 none non-standard — Details →
3.0.131 25 Oct 2025 none non-standard — Details →
3.0.130 24 Oct 2025 none non-standard — Details →
3.0.129 19 Oct 2025 none non-standard — Details →
3.0.127 07 Oct 2025 none non-standard — Details →
3.0.126 29 Sep 2025 none non-standard — Details →
3.0.125 25 Sep 2025 none non-standard — Details →
3.0.124 21 Sep 2025 none non-standard — Details →
3.0.122 13 Sep 2025 none non-standard — Details →
3.0.121 12 Sep 2025 none non-standard — Details →
3.0.120 03 Sep 2025 none non-standard — Details →
3.0.118 31 Aug 2025 none non-standard — Details →
3.0.116 24 Aug 2025 none non-standard — Details →
3.0.113 12 Aug 2025 none non-standard — Details →
3.0.112 09 Aug 2025 none non-standard — Details →
3.0.108 27 Jul 2025 none non-standard — Details →
3.0.105 09 Jul 2025 none non-standard — Details →
3.0.104 03 Jul 2025 none non-standard — Details →
3.0.103 02 Jul 2025 none non-standard — Details →
3.0.102 24 Jun 2025 none non-standard — Details →
3.0.101 22 Jun 2025 none non-standard — Details →
3.0.99 19 Jun 2025 none non-standard — Details →
3.0.92 01 Jun 2025 none non-standard — Details →
3.0.91 13 May 2025 none non-standard — Details →
3.0.89 01 May 2025 none non-standard — Details →
3.0.87 22 Apr 2025 none non-standard — Details →
3.0.85 16 Apr 2025 none non-standard — Details →
3.0.83 10 Apr 2025 none non-standard — Details →
3.0.82 07 Apr 2025 none non-standard — Details →
3.0.81 07 Apr 2025 none non-standard — Details →
3.0.79 02 Apr 2025 none non-standard — Details →
3.0.76 25 Mar 2025 none non-standard — Details →
3.0.74 21 Mar 2025 none non-standard — Details →
3.0.69 14 Mar 2025 none non-standard — Details →
3.0.68 07 Mar 2025 none non-standard — Details →
3.0.66 02 Mar 2025 none non-standard — Details →
3.0.64 01 Mar 2025 none non-standard — Details →
3.0.61 26 Feb 2025 none non-standard — Details →
3.0.59 17 Feb 2025 none non-standard — Details →
3.0.55 13 Feb 2025 none non-standard — Details →
3.0.53 09 Feb 2025 none non-standard — Details →
3.0.49 29 Jan 2025 none non-standard — Details →
3.0.48 26 Jan 2025 none non-standard — Details →
3.0.46 24 Jan 2025 none non-standard — Details →
3.0.45 23 Jan 2025 none non-standard — Details →
3.0.40 18 Jan 2025 none non-standard — Details →
3.0.38 12 Jan 2025 none non-standard — Details →
3.0.36 03 Jan 2025 none non-standard — Details →
3.0.35 17 Dec 2024 none non-standard — Details →
3.0.33 13 Dec 2024 none non-standard — Details →

All 78 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 library

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 library

Is library safe to use?

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

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

No. 4.0.0, 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 library have?

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

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

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