VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pyobjc-core: vulnerability history, versions and safety

pyobjc-core 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 pyobjc-core vulnerabilities

Vulert verdict on pyobjc-core 12.2.2 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Inactive

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

  • Current release 12.2.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 406 packages i
  • Stars 823 i
  • OpenSSF scorecard 1/10 i
  • Last release 2 months ago 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 pyobjc-core, 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
12.2.2 11 Aug 2026 none MIT — Details →
12.2.1 19 Jun 2026 none MIT — Details →
12.2.0 30 May 2026 none MIT — Details →
12.1.0 14 Nov 2025 none MIT — Details →
12.0.0 21 Oct 2025 none MIT — Details →
11.1.0 14 Jun 2025 none MIT — Details →
11.0.0 14 Jan 2025 none MIT — Details →
10.3.2 30 Nov 2024 none MIT — Details →
10.3.1 11 Jun 2024 none MIT — Details →
10.3.0 28 May 2024 none MIT — Details →
10.2.0 16 Mar 2024 none MIT — Details →
10.1.0 09 Dec 2023 none MIT — Details →
10.0.0 24 Sep 2023 none MIT — Details →
9.2.0 07 Jun 2023 none MIT — Details →
9.1.1 18 Apr 2023 none MIT — Details →
9.1.0 16 Apr 2023 none MIT — Details →
9.1.0b1 03 Apr 2023 none MIT — Details →
9.0.1 19 Dec 2022 none MIT — Details →
9.0.0 05 Nov 2022 none MIT — Details →
8.5.1 18 Sep 2022 none MIT — Details →
8.5.0 19 Apr 2022 none MIT — Details →
8.4.1 15 Mar 2022 none MIT — Details →
8.4.0 07 Mar 2022 none MIT — Details →
8.3.0 24 Feb 2022 none MIT — Details →
8.2.0 23 Jan 2022 none MIT — Details →
8.1.0 29 Nov 2021 none MIT — Details →
8.0.0 11 Nov 2021 none MIT — Details →
8.0.0b1 20 Sep 2021 none MIT — Details →
7.3.0 07 Jun 2021 none MIT — Details →
7.2.0 01 May 2021 none MIT — Details →
7.1.0 29 Dec 2020 none MIT — Details →
7.0.1 30 Nov 2020 none MIT — Details →
7.0.0 29 Nov 2020 none MIT — Details →
6.2.2 08 Jul 2020 none MIT — Details →
6.2.1 14 Jun 2020 none MIT — Details →
6.2.0 25 Mar 2020 none MIT — Details →
6.1.0 06 Nov 2019 none MIT — Details →
6.0.1 20 Oct 2019 none MIT — Details →
6.0.0 17 Oct 2019 none MIT — Details →
5.3.0 16 Oct 2019 none MIT — Details →
5.2.0 03 Apr 2019 none MIT — Details →
5.1.2 13 Dec 2018 none MIT — Details →
5.1.1 31 Oct 2018 none MIT — Details →
5.1.0 16 Oct 2018 none MIT — Details →
5.0.0 18 Sep 2018 none MIT — Details →
5.0.0b1 02 Sep 2018 none MIT — Details →
5.0.0a1 05 Aug 2018 none MIT — Details →
4.2.2 04 Jun 2018 none MIT — Details →
4.2.1 03 Apr 2018 none MIT — Details →
4.2.0 01 Apr 2018 none MIT — Details →
4.1.0 06 Dec 2017 none MIT — Details →
4.0.1 20 Nov 2017 none MIT — Details →
4.0.0 25 Sep 2017 none MIT — Details →
4.0.0b1 27 Aug 2017 none MIT — Details →
3.2.1 12 Dec 2016 none MIT — Details →
3.2.1b1 12 Dec 2016 none MIT — Details →
3.2.0 06 Dec 2016 none MIT — Details →
3.1.1 28 Mar 2016 none MIT — Details →
3.1.0 28 Mar 2016 none MIT — Details →
3.0.4 07 Dec 2014 none MIT — Details →
3.0.3 22 Oct 2014 none MIT — Details →
3.0.1 27 Jul 2014 none MIT — Details →
2.5.1 22 Jan 2013 none MIT — Details →
2.4.0 01 Nov 2012 none MIT — Details →
2.3.0 29 Jul 2010 none MIT — Details →
2.2.0 24 Nov 2009 none MIT — Details →
2.2.0b2 26 May 2009 none MIT — Details →
2.2.0b1 08 Mar 2009 none MIT — Details →
2.2-py2.6-macosx-10.3-fat — none — — Details →
2.2b2-py2.6-macosx-10.3-fat — none — — Details →
2.3-py2.6-macosx-10.6-fat — none — — Details →
2.3-py2.7-macosx-10.6-fat — none — — Details →
2.3-py3.1-macosx-10.6-fat — none — — Details →
2.3-py3.2-macosx-10.6-fat — none — — Details →
4.0.1b1 — none — — Details →

All 75 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 pyobjc-core

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 pyobjc-core

Is pyobjc-core safe to use?

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

Vulert scores pyobjc-core 75/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 pyobjc-core affected?

No. 12.2.2, 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 pyobjc-core should I use?

12.2.2 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 pyobjc-core have?

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

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

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