VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

oslo-i18n: vulnerability history, versions and safety

oslo-i18n 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 oslo-i18n vulnerabilities

Vulert verdict on oslo-i18n 6.9.0 i

Updated on 23 Oct 2026

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

Package health score 94/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Not enough data

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

  • Current release 6.9.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 611 packages i
  • Last release 3 months ago i
  • Licence Apache-2.0 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 oslo-i18n, 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
6.9.0 10 Jul 2026 none Apache-2.0 — Details →
6.8.0 18 May 2026 none Apache-2.0 — Details →
6.7.2 17 Feb 2026 none Apache-2.0 — Details →
6.7.1 20 Nov 2025 none Apache-2.0 — Details →
6.7.0 13 Nov 2025 none Apache-2.0 — Details →
6.6.0 25 Aug 2025 none Apache-2.0 — Details →
6.1.1 24 Feb 2025 none Apache-2.0 — Details →
6.5.1 21 Feb 2025 none Apache-2.0 — Details →
6.5.0 19 Nov 2024 none non-standard — Details →
6.4.0 21 Aug 2024 none non-standard — Details →
6.3.0 22 Feb 2024 none non-standard — Details →
6.2.0 14 Nov 2023 none non-standard — Details →
6.1.0 28 Aug 2023 none non-standard — Details →
6.0.0 10 Feb 2023 none non-standard — Details →
5.1.0 06 Sep 2021 none non-standard — Details →
5.0.1 11 Sep 2020 none non-standard — Details →
5.0.0 04 Jun 2020 none non-standard — Details →
4.0.1 07 Apr 2020 none non-standard — Details →
4.0.0 13 Feb 2020 none non-standard — Details →
3.25.1 06 Jan 2020 none non-standard — Details →
3.25.0 25 Nov 2019 none non-standard — Details →
3.24.0 04 Sep 2019 none non-standard — Details →
3.17.2 16 Apr 2019 none non-standard — Details →
3.23.1 28 Feb 2019 none non-standard — Details →
3.23.0 28 Nov 2018 none non-standard — Details →
3.22.1 25 Sep 2018 none non-standard — Details →
3.22.0 24 Sep 2018 none non-standard — Details →
3.21.0 20 Jul 2018 none non-standard — Details →
3.20.0 14 Mar 2018 none non-standard — Details →
3.19.0 04 Dec 2017 none non-standard — Details →
3.17.1 20 Nov 2017 none non-standard — Details →
3.18.0 20 Sep 2017 none non-standard — Details →
3.17.0 18 Jul 2017 none non-standard — Details →
3.16.0 10 Jul 2017 none non-standard — Details →
3.15.3 23 May 2017 none non-standard — Details →
3.15.2 22 May 2017 none non-standard — Details →
3.15.1 15 May 2017 none non-standard — Details →
3.15.0 28 Mar 2017 none non-standard — Details →
3.14.0 13 Mar 2017 none non-standard — Details →
3.13.0 06 Mar 2017 none non-standard — Details →
3.12.0 18 Jan 2017 none non-standard — Details →
3.11.0 01 Dec 2016 none non-standard — Details →
3.10.0 19 Oct 2016 none non-standard — Details →
3.9.0 18 Aug 2016 none non-standard — Details →
3.8.0 13 Jul 2016 none non-standard — Details →
3.7.0 10 Jun 2016 none non-standard — Details →
3.6.0 21 Apr 2016 none non-standard — Details →
3.5.0 28 Mar 2016 none non-standard — Details →
3.4.0 25 Feb 2016 none non-standard — Details →
3.3.0 09 Feb 2016 none non-standard — Details →
3.2.0 14 Jan 2016 none non-standard — Details →
3.1.0 07 Dec 2015 none non-standard — Details →
3.0.0 23 Nov 2015 none non-standard — Details →
2.7.0 12 Oct 2015 none non-standard — Details →
2.6.0 08 Sep 2015 none non-standard — Details →
2.5.0 24 Aug 2015 none non-standard — Details →
2.4.0 18 Aug 2015 none non-standard — Details →
2.3.0 03 Aug 2015 none non-standard — Details →
2.2.0 27 Jul 2015 none non-standard — Details →
2.1.0 06 Jul 2015 none non-standard — Details →
2.0.0 23 Jun 2015 none non-standard — Details →
1.7.0 02 Jun 2015 none non-standard — Details →
1.6.0 21 Apr 2015 none non-standard — Details →
1.5.0 09 Mar 2015 none non-standard — Details →
1.4.0 16 Feb 2015 none non-standard — Details →
1.3.1 27 Jan 2015 none non-standard — Details →
1.3.0 08 Jan 2015 none non-standard — Details →
1.2.0 06 Jan 2015 none non-standard — Details →
1.1.0 02 Dec 2014 none non-standard — Details →
1.0.0 18 Sep 2014 none non-standard — Details →
0.4.0 15 Sep 2014 none non-standard — Details →
0.3.0 08 Sep 2014 none non-standard — Details →
0.2.0 18 Aug 2014 none non-standard — Details →
0.1.0 02 Jul 2014 none non-standard — Details →

All 74 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 oslo-i18n

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 oslo-i18n

Is oslo-i18n safe to use?

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

Vulert scores oslo-i18n 94/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 oslo-i18n affected?

No. 6.9.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 oslo-i18n should I use?

6.9.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 oslo-i18n have?

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

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

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