Certifi is a Python package that provides a curated bundle of Mozilla Root Certificates for validating SSL certificates and verifying the identity of TLS hosts. It is useful when you want a reliable, portable CA trust store for Python applications, and it does not support adding or modifying the certificates, so alternate trust should come from other tooling.
Project status
- Actively maintained: The upstream repo shows a recent push (2026-06-03), and the most recent published update in this stream is 2026-05-20, which is only a few weeks before today (2026-06-11).
- Update cadence: Updates appear to be fairly regular, roughly monthly to every couple of months (2025-10-05, 2025-11-12, 2026-01-04, 2026-02-25, 2026-04-22, 2026-05-20, plus a 2026-06-03 upstream push).
AI summary generated 2026-06-11
Recent updates
2026.05.20
2026-05-20This release updates the certifi package version from 2026.04.22 to 2026.05.20. It also removes a CA certificate from the bundled default trust store (cacert.pem). No release notes were provided by the publisher to describe these changes.
2026.04.22
2026-04-22Release 2026.04.22 updates certifi's bundled CA certificate file and refreshes the project packaging and release automation. It also adds new public API surface (certifi.contents) and a small CLI entry point, alongside internal refactoring of how cacert.pem is located and loaded.
BreakingSecurityFeatures2026.02.25
2026-02-25This release updates the packaged certifi trust store and bumps the library version. There are also CI and automation workflow updates to newer GitHub Actions versions used by the project.
Security2026.01.04
2026-01-04Release 2026.01.04 updates the project version, refreshes GitHub Actions workflow dependencies, and updates the bundled CA certificate file (certifi/cacert.pem). The publisher provided no release notes, so changes are effectively undocumented here.
BreakingSecurity2025.11.12
2025-11-12This release updates the package version metadata and modifies the GitHub Actions workflow used to build and publish distribution artifacts. The largest functional change is in the bundled CA certificate file, where a substantial number of certificate entries were removed from certifi/cacert.pem.
Security2025.10.05
2025-10-05Release 2025.10.05 updates the packaged CA trust store (certifi's cacert.pem), bumps the library version metadata, and refreshes CI and release GitHub Actions to newer major versions. No publisher release notes were provided, so the changes below reflect only what is present in the code diff.
2025.08.03
2025-08-03Release 2025.08.03 updates the certifi package version and modifies the bundled CA certificate bundle. The code diff shows the CA bundle (cacert.pem) lost a large certificate entry and only a small amount of Python code changed (version string).
BreakingSecurity2025.07.14
2025-07-14This release is effectively a certifi update. The only code changes are bumping certifi's reported version string and updating the bundled CA certificate bundle (cacert.pem) with additional certificates.
Security2025.07.09
2025-07-09This release updates the certifi Python package version to 2025.07.09 and makes substantial packaging and internal implementation changes. It also introduces new public API surface (the cert contents accessor) and adds typing support, while updating the bundled CA bundle file itself.
BreakingFeatures2025.06.15
2025-06-15This release (2025.06.15) does not include any release notes or change descriptions from the publisher. As a result, there is no documented information on new features, fixes, breaking changes, or dependency updates that could impact developers.
v1.0.1
2014-03-10v1.0.1 updates the certifi package version and refreshes the bundled CA certificate file. The release notes are not provided, so the diff suggests multiple functional changes, most importantly to the CA trust store used for TLS verification.
BreakingFeaturesv1.0.0
2014-01-17The release notes for v1.0.0 were not provided, so no documented changes can be extracted. Based on the absence of release notes, developers should review the v1.0.0 tag diff against their current version to identify API, behavior, and configuration changes.