VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

librosa: vulnerability history, versions and safety

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

Vulert verdict on librosa 1.0.0 i

Updated on 23 Oct 2026

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

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,280 packages i
  • Stars 8,693 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence ISC 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 librosa, 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
1.0.0 11 Aug 2026 none ISC — Details →
1.0.0rc0 31 Jul 2026 none ISC — Details →
0.11.0 11 Mar 2025 none ISC — Details →
0.11.0rc1 21 Feb 2025 none ISC — Details →
0.11.0rc0 11 Feb 2025 none ISC — Details →
0.10.2.post1 14 May 2024 none ISC — Details →
0.10.2 02 May 2024 none ISC — Details →
0.10.1 16 Aug 2023 none ISC — Details →
0.10.0.post2 17 Mar 2023 none ISC — Details →
0.10.0.post1 16 Mar 2023 none ISC — Details →
0.10.0 20 Feb 2023 none ISC — Details →
0.10.0rc1 17 Feb 2023 none ISC — Details →
0.10.0rc0 07 Feb 2023 none ISC — Details →
0.9.2 27 Jun 2022 none ISC — Details →
0.9.1 15 Feb 2022 none ISC — Details →
0.9.0 07 Feb 2022 none ISC — Details →
0.9.0rc0 31 Jan 2022 none ISC — Details →
0.8.1 26 May 2021 none ISC — Details →
0.8.1rc2 25 May 2021 none ISC — Details →
0.8.1rc1 23 May 2021 none ISC — Details →
0.8.0 22 Jul 2020 none ISC — Details →
0.7.2 13 Jan 2020 none ISC — Details →
0.7.1 09 Oct 2019 none ISC — Details →
0.7.0 08 Jul 2019 none ISC — Details →
0.7.0rc1 01 Jul 2019 none ISC — Details →
0.6.3 13 Feb 2019 none ISC — Details →
0.6.2 09 Aug 2018 none ISC — Details →
0.6.1 24 May 2018 none ISC — Details →
0.6.1rc0 22 May 2018 none ISC — Details →
0.6.0 17 Feb 2018 none ISC — Details →
0.6.0rc1 13 Feb 2018 none ISC — Details →
0.6.0rc0 10 Feb 2018 none ISC — Details →
0.5.1 08 May 2017 none ISC — Details →
0.5.0 17 Feb 2017 none ISC — Details →
0.5.0rc0 11 Feb 2017 none ISC — Details →
0.4.3 17 May 2016 none ISC — Details →
0.4.3rc0 15 May 2016 none ISC — Details →
0.4.2 20 Feb 2016 none ISC — Details →
0.4.1 17 Oct 2015 none ISC — Details →
0.4.1rc0 14 Oct 2015 none ISC — Details →
0.4.0 07 Jun 2015 none ISC — Details →
0.4.0rc2 23 May 2015 none ISC — Details →
0.3.1 14 Nov 2014 none non-standard — Details →
0.3.0 30 Jun 2014 none non-standard — Details →
0.2.1 24 Jan 2014 none non-standard — Details →
0.2.0 14 Dec 2013 none non-standard — Details →
0.2.0-py2.7 — none — — Details →
0.2.0.linux-x86_64 — none — — Details →
0.2.1.linux-x86_64 — none — — 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 librosa

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 librosa

Is librosa safe to use?

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

Vulert scores librosa 86/100, which reads as healthy. 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 librosa affected?

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

Which version of librosa should I use?

1.0.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 librosa have?

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

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

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