VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pre-commit: vulnerability history, versions and safety

pre-commit 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 pre-commit vulnerabilities

Vulert verdict on pre-commit 4.7.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.7.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,314 packages i
  • Stars 15,640 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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 pre-commit, 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.7.0 12 Oct 2026 none MIT — Details →
4.6.2 10 Aug 2026 none MIT — Details →
4.6.1 21 Jul 2026 none MIT — Details →
4.6.0 21 Apr 2026 none MIT — Details →
4.5.1 16 Dec 2025 none MIT — Details →
4.5.0 22 Nov 2025 none MIT — Details →
4.4.0 08 Nov 2025 none MIT — Details →
4.3.0 09 Aug 2025 none MIT — Details →
4.2.0 18 Mar 2025 none MIT — Details →
4.1.0 20 Jan 2025 none MIT — Details →
4.0.1 08 Oct 2024 none MIT — Details →
4.0.0 05 Oct 2024 none MIT — Details →
3.8.0 28 Jul 2024 none MIT — Details →
3.7.1 11 May 2024 none MIT — Details →
3.7.0 24 Mar 2024 none MIT — Details →
3.6.2 18 Feb 2024 none MIT — Details →
3.6.1 10 Feb 2024 none MIT — Details →
3.6.0 09 Dec 2023 none MIT — Details →
3.5.0 13 Oct 2023 none MIT — Details →
3.4.0 02 Sep 2023 none MIT — Details →
3.3.3 13 Jun 2023 none MIT — Details →
3.3.2 17 May 2023 none MIT — Details →
3.3.1 02 May 2023 none MIT — Details →
3.3.0 01 May 2023 none MIT — Details →
3.2.2 03 Apr 2023 none MIT — Details →
3.2.1 25 Mar 2023 none MIT — Details →
3.2.0 17 Mar 2023 none MIT — Details →
3.1.1 28 Feb 2023 none MIT — Details →
3.1.0 23 Feb 2023 none MIT — Details →
3.0.4 03 Feb 2023 none MIT — Details →
3.0.3 01 Feb 2023 none MIT — Details →
3.0.2 29 Jan 2023 none MIT — Details →
3.0.1 26 Jan 2023 none MIT — Details →
3.0.0 24 Jan 2023 none MIT — Details →
2.21.0 25 Dec 2022 none MIT — Details →
2.20.0 11 Jul 2022 none MIT — Details →
2.19.0 05 May 2022 none MIT — Details →
2.18.1 03 Apr 2022 none MIT — Details →
2.18.0 02 Apr 2022 none MIT — Details →
2.17.0 18 Jan 2022 none MIT — Details →
2.16.0 30 Nov 2021 none MIT — Details →
2.15.0 03 Sep 2021 none MIT — Details →
2.14.1 28 Aug 2021 none MIT — Details →
2.14.0 06 Aug 2021 none MIT — Details →
2.13.0 21 May 2021 none MIT — Details →
2.12.1 16 Apr 2021 none MIT — Details →
2.12.0 06 Apr 2021 none MIT — Details →
2.11.1 10 Mar 2021 none MIT — Details →
2.11.0 07 Mar 2021 none MIT — Details →
2.10.1 06 Feb 2021 none MIT — Details →
2.10.0 27 Jan 2021 none MIT — Details →
2.9.3 07 Dec 2020 none MIT — Details →
2.9.2 26 Nov 2020 none MIT — Details →
2.9.1 25 Nov 2020 none MIT — Details →
2.9.0 21 Nov 2020 none MIT — Details →
2.8.2 30 Oct 2020 none MIT — Details →
2.8.1 29 Oct 2020 none MIT — Details →
2.8.0 29 Oct 2020 none MIT — Details →
2.7.1 23 Aug 2020 none MIT — Details →
2.7.0 22 Aug 2020 none MIT — Details →
2.6.0 01 Jul 2020 none MIT — Details →
2.5.1 09 Jun 2020 none MIT — Details →
2.5.0 08 Jun 2020 none MIT — Details →
2.4.0 11 May 2020 none MIT — Details →
2.3.0 22 Apr 2020 none MIT — Details →
2.2.0 12 Mar 2020 none MIT — Details →
2.1.1 24 Feb 2020 none MIT — Details →
2.1.0 18 Feb 2020 none MIT — Details →
2.0.1 30 Jan 2020 none MIT — Details →
2.0.0 29 Jan 2020 none MIT — Details →
1.21.0 02 Jan 2020 none MIT — Details →
1.20.0 28 Oct 2019 none MIT — Details →
1.19.0 26 Oct 2019 none MIT — Details →
1.18.3 27 Aug 2019 none MIT — Details →
1.18.2 15 Aug 2019 none MIT — Details →
1.18.1 11 Aug 2019 none MIT — Details →
1.18.0 03 Aug 2019 none MIT — Details →
1.17.0 06 Jun 2019 none MIT — Details →
1.16.1 08 May 2019 none MIT — Details →
1.16.0 04 May 2019 none MIT — Details →
1.15.2 16 Apr 2019 none MIT — Details →
1.15.1 01 Apr 2019 none MIT — Details →
1.15.0 30 Mar 2019 none MIT — Details →
1.14.4 18 Feb 2019 none MIT — Details →
1.14.3 04 Feb 2019 none MIT — Details →
1.14.2 11 Jan 2019 none MIT — Details →
1.14.1 10 Jan 2019 none MIT — Details →
1.14.0 08 Jan 2019 none MIT — Details →
1.13.0 20 Dec 2018 none MIT — Details →
1.12.0 23 Oct 2018 none MIT — Details →
1.11.2 11 Oct 2018 none MIT — Details →
1.11.1 22 Sep 2018 none MIT — Details →
1.11.0 03 Sep 2018 none MIT — Details →
1.10.5 06 Aug 2018 none MIT — Details →
1.10.4 22 Jul 2018 none MIT — Details →
1.10.3 02 Jul 2018 none MIT — Details →
1.10.2 11 Jun 2018 none MIT — Details →
1.10.1 29 May 2018 none MIT — Details →
1.10.0 26 May 2018 none MIT — Details →
1.9.0 22 May 2018 none MIT — Details →
1.8.2 18 Mar 2018 none — — Details →
1.8.1 12 Mar 2018 none — — Details →
1.8.0 12 Mar 2018 none — — Details →
1.7.0 04 Mar 2018 none — — Details →
1.6.0 04 Feb 2018 none — — Details →
1.5.1 24 Jan 2018 none — — Details →
1.5.0 14 Jan 2018 none — — Details →
1.4.5 09 Jan 2018 none — — Details →
1.4.4 08 Jan 2018 none — — Details →
1.4.3 03 Jan 2018 none — — Details →
1.4.2 02 Jan 2018 none — — Details →
1.4.1 09 Nov 2017 none — — Details →
1.4.0 08 Nov 2017 none — — Details →
1.3.0 08 Oct 2017 none — — Details →
1.2.0 04 Oct 2017 none — — Details →
1.1.2 20 Sep 2017 none — — Details →
1.1.1 18 Sep 2017 none — — Details →
1.1.0 11 Sep 2017 none — — Details →
1.0.1 07 Sep 2017 none — — Details →
1.0.0 07 Sep 2017 none — — Details →

The newest 120 of 205 versions Vulert tracks. 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 pre-commit

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 pre-commit

Is pre-commit safe to use?

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

Vulert scores pre-commit 88/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 pre-commit affected?

No. 4.7.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 pre-commit should I use?

4.7.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 pre-commit have?

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

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

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