VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

semver: vulnerability history, versions and safety

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

Vulert verdict on semver 3.1.0 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 3,048 packages i
  • Stars 526 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month 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 semver, 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.1.0 12 Sep 2026 none non-standard — Details →
3.0.4 24 Jan 2025 none non-standard — Details →
3.0.3 18 Jan 2025 none non-standard — Details →
3.0.2 09 Oct 2023 none non-standard — Details →
3.0.1 14 Jun 2023 none non-standard — Details →
3.0.0 02 Apr 2023 none non-standard — Details →
3.0.0rc1 19 Mar 2023 none non-standard — Details →
3.0.0.dev4 19 Dec 2022 none non-standard — Details →
3.0.0.dev3 20 Jan 2022 none non-standard — Details →
3.0.0.dev2 01 Nov 2020 none non-standard — Details →
3.0.0.dev1 26 Oct 2020 none non-standard — Details →
2.13.0 20 Oct 2020 none non-standard — Details →
2.12.0 19 Oct 2020 none non-standard — Details →
2.11.0 17 Oct 2020 none non-standard — Details →
2.10.2 15 Jun 2020 none non-standard — Details →
2.10.1 13 May 2020 none non-standard — Details →
2.10.0 05 May 2020 none non-standard — Details →
2.9.1 16 Feb 2020 none non-standard — Details →
2.9.0 30 Oct 2019 none non-standard — Details →
2.8.1 09 Jul 2018 none non-standard — Details →
2.8.0 16 May 2018 none non-standard — Details →
2.7.9 23 Sep 2017 none non-standard — Details →
2.7.8 25 Aug 2017 none non-standard — Details →
2.7.7 25 May 2017 none non-standard — Details →
2.7.6 28 Feb 2017 none non-standard — Details →
2.7.5 29 Jan 2017 none non-standard — Details →
2.7.4 16 Jan 2017 none — — Details →
2.7.3 19 Dec 2016 none — — Details →
2.7.2 08 Nov 2016 none non-standard — Details →
2.7.1 20 Oct 2016 none non-standard — Details →
2.7.0 20 Oct 2016 none non-standard — Details →
2.6.0 07 Jun 2016 none non-standard — Details →
2.5.0 24 May 2016 none non-standard — Details →
2.4.2 15 May 2016 none non-standard — Details →
2.4.1 03 Mar 2016 none non-standard — Details →
2.4.0 11 Feb 2016 none non-standard — Details →
2.3.1 29 Jan 2016 none non-standard — Details →
2.3.0 28 Jan 2016 none non-standard — Details →
2.2.1 03 Aug 2015 none non-standard — Details →
2.2.0 20 Jun 2015 none non-standard — Details →
2.1.2 22 May 2015 none non-standard — Details →
2.1.1 22 May 2015 none non-standard — Details →
2.1.0 22 May 2015 none non-standard — Details →
2.0.2 14 Apr 2015 none non-standard — Details →
2.0.1 24 Sep 2014 none non-standard — Details →
2.0.0 12 Sep 2014 none non-standard — Details →
0.0.2 09 May 2012 none non-standard — Details →
0.0.1 09 May 2012 none non-standard — Details →
2.0.2.macosx-10.10-x86_64 — none — — Details →
2.1.0.macosx-10.10-x86_64 — none — — Details →
2.1.1.macosx-10.10-x86_64 — none — — Details →
2.1.2.macosx-10.10-x86_64 — none — — Details →
2.2.0.macosx-10.10-x86_64 — none — — Details →
2.2.1.macosx-10.10-x86_64 — none — — Details →
2.3.0.macosx-10.11-x86_64 — none — — Details →
2.3.1.macosx-10.11-x86_64 — none — — Details →
2.4.0.macosx-10.11-x86_64 — none — — Details →
2.4.1.macosx-10.11-x86_64 — none — — Details →
2.4.2.macosx-10.11-x86_64 — none — — Details →
2.5.0.macosx-10.11-x86_64 — none — — Details →
2.6.0.macosx-10.11-x86_64 — none — — Details →
2.7.0.macosx-10.11-x86_64 — none — — Details →
2.7.1.macosx-10.11-x86_64 — none — — Details →
2.7.2.macosx-10.11-x86_64 — none — — Details →
2.7.3.macosx-10.11-x86_64 — none — — Details →
2.7.4.macosx-10.11-x86_64 — none — — Details →
2.7.5.macosx-10.11-x86_64 — none — — Details →
2.7.6.macosx-10.11-x86_64 — none — — Details →
2.7.7.macosx-10.11-x86_64 — none — — Details →
2.7.8.macosx-10.11-x86_64 — none — — Details →

All 70 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 semver

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 semver

Is semver safe to use?

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

Vulert scores semver 84/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 semver affected?

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

Which version of semver should I use?

3.1.0 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 semver have?

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

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

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