VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

yamllint: vulnerability history, versions and safety

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

Vulert verdict on yamllint 1.38.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.38.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 170 packages i
  • Stars 3,479 i
  • OpenSSF scorecard 4/10 i
  • Last release 9 months ago i
  • Licence GPL-3.0-or-later 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 yamllint, 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.38.0 13 Jan 2026 none GPL-3.0-or-later — Details →
1.37.1 04 May 2025 none GPL-3.0-or-later — Details →
1.37.0 23 Mar 2025 none GPL-3.0-or-later — Details →
1.36.2 17 Mar 2025 none GPL-3.0-or-later — Details →
1.36.1 15 Mar 2025 none GPL-3.0-or-later — Details →
1.36.0 11 Mar 2025 none GPL-3.0-or-later — Details →
1.35.1 16 Feb 2024 none GPL-3.0-or-later — Details →
1.35.0 15 Feb 2024 none GPL-3.0-or-later — Details →
1.34.0 06 Feb 2024 none GPL-3.0-or-later — Details →
1.33.0 09 Nov 2023 none GPL-3.0-or-later — Details →
1.32.0 22 May 2023 none GPL-3.0-only — Details →
1.31.0 21 Apr 2023 none GPL-3.0-only — Details →
1.30.0 22 Mar 2023 none GPL-3.0 — Details →
1.29.0 10 Jan 2023 none GPL-3.0 — Details →
1.28.0 11 Oct 2022 none GPL-3.0 — Details →
1.27.1 08 Jul 2022 none GPL-3.0 — Details →
1.27.0 08 Jul 2022 none GPL-3.0 — Details →
1.26.3 21 Aug 2021 none GPL-3.0 — Details →
1.26.2 03 Aug 2021 none GPL-3.0 — Details →
1.26.1 06 Apr 2021 none GPL-3.0 — Details →
1.26.0 29 Jan 2021 none GPL-3.0 — Details →
1.25.0 29 Sep 2020 none GPL-3.0 — Details →
1.24.2 16 Jul 2020 none GPL-3.0 — Details →
1.24.1 15 Jul 2020 none GPL-3.0 — Details →
1.24.0 15 Jul 2020 none GPL-3.0 — Details →
1.23.0 17 Apr 2020 none GPL-3.0 — Details →
1.22.1 15 Apr 2020 none GPL-3.0 — Details →
1.22.0 13 Apr 2020 none GPL-3.0 — Details →
1.21.0 24 Mar 2020 none GPL-3.0 — Details →
1.20.0 26 Dec 2019 none GPL-3.0 — Details →
1.19.0 19 Nov 2019 none GPL-3.0 — Details →
1.18.0 15 Oct 2019 none GPL-3.0 — Details →
1.17.0 12 Aug 2019 none GPL-3.0 — Details →
1.16.0 07 Jun 2019 none GPL-3.0 — Details →
1.15.0 11 Feb 2019 none GPL-3.0 — Details →
1.14.0 14 Jan 2019 none GPL-3.0 — Details →
1.13.0 14 Nov 2018 none GPL-3.0 — Details →
1.12.1 17 Oct 2018 none GPL-3.0 — Details →
1.12.0 04 Oct 2018 none GPL-3.0 — Details →
1.11.1 06 Apr 2018 none GPL-3.0 — Details →
1.11.0 21 Feb 2018 none GPL-3.0 — Details →
1.10.0 05 Nov 2017 none GPL-3.0 — Details →
1.9.0 16 Oct 2017 none GPL-3.0 — Details →
1.8.2 10 Oct 2017 none GPL-3.0 — Details →
1.8.1 04 Jul 2017 none GPL-3.0 — Details →
1.8.0 28 Jun 2017 none GPL-3.0 — Details →
1.7.0 25 Apr 2017 none GPL-3.0 — Details →
1.6.1 25 Feb 2017 none GPL-3.0 — Details →
1.6.0 30 Nov 2016 none GPL-3.0 — Details →
1.5.0 14 Oct 2016 none GPL-3.0 — Details →
1.4.1 27 Sep 2016 none GPL-3.0 — Details →
1.4.0 19 Sep 2016 none GPL-3.0 — Details →
1.3.2 28 Jun 2016 none GPL-3.0 — Details →
1.3.1 28 Jun 2016 none GPL-3.0 — Details →
1.3.0 27 Jun 2016 none GPL-3.0 — Details →
1.2.2 24 Jun 2016 none GPL-3.0 — Details →
1.2.1 25 Mar 2016 none GPL-3.0 — Details →
1.2.0 06 Mar 2016 none GPL-3.0 — Details →
1.1.0 04 Mar 2016 none GPL-3.0 — Details →
1.0.4 04 Mar 2016 none GPL-3.0 — Details →
1.0.3 25 Feb 2016 none GPL-3.0 — Details →
1.0.2 24 Feb 2016 none GPL-3.0 — Details →
1.0.1 19 Feb 2016 none GPL-3.0 — Details →
1.0.0 19 Feb 2016 none GPL-3.0 — Details →
0.7.2 05 Feb 2016 none GPL-3.0 — Details →
0.7.1 03 Feb 2016 none GPL-3.0 — Details →
0.7.0 01 Feb 2016 none GPL-3.0 — Details →
0.6.0 25 Jan 2016 none GPL-3.0 — Details →
0.5.2 24 Jan 2016 none GPL-3.0 — Details →
0.5.1 24 Jan 2016 none GPL-3.0 — Details →
0.5.0 23 Jan 2016 none GPL-3.0 — Details →
0.4.0 20 Jan 2016 none GPL-3.0 — Details →
0.2.0 15 Jan 2016 none GPL-3.0 — Details →
0.1.0 12 Jan 2016 none GPL-3.0 — 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 yamllint

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 yamllint

Is yamllint safe to use?

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

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

No. 1.38.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 yamllint should I use?

1.38.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 yamllint have?

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

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

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