NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #4414 most downloaded on Packagist
Up-to-date, verifiable repository for Certificate Authorities
Latest stable
v3.0.3
Last release 1 months ago
20 Oct 2026
Release timing varies
gaps range from 2 weeks to 2.5 years
Most releases are documented
notes for 27 of 31 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
31 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
https://emudhra.we-have-a-problem.com/
https://emudhra.we-have-a-problem.com/
Ignore tests, workflows and .MD docs with "export-ignore" on .gitattr by @erikn69 in #44
Full Changelog: v3.0.1...v3.0.2
Full Changelog: https://github.com/paragonie/certainty/compare/v3.0.1...v3.0.2
Your coding agent can read these notes before it upgrades. Set up the MCP server →
More nullable fixes missed in previous update.
More nullable fixes missed in previous update.
This fixes deprecation warnings in PHP 8.4, but drops support for PHP < 8.3.
This fixes deprecation warnings in PHP 8.4, but drops support for PHP < 8.3.
This fixes deprecation warnings in PHP 8.4, but drops support for PHP < 8.3.
Updates DNS to use pie-hosted.net rather than pie-hosted.com .
pie-hosted.net rather than pie-hosted.com.The primary signing key was rotated!
The device that contained the signing key has been destroyed, so we have promoted our backup key to the primary one and generated a new backup keypair.
Nothing published for this version
What's Changed Fix CI Prune old files Full Changelog : v2.8.2...v2.8.3
No code changes, just includes the latest CACert bundles, including the bundle after LetsEncrypt's intermediate certificate expired .
Block vulnerable versions of Composer.
#32 / #33 -- Add support for Guzzle 7 (thanks @jacques , @ziming )
Updated Psalm in require-dev from ^1|^2 to ^1|^3.
Expand unit testing coverage to PHP 7.4
We had to reinstall the server. Bgcc1QfkP0UNgMZuHzi0hC1hA1SoVAyUrskmSkzRw3E= is the public key of the new default Chronicle server.
We had to reinstall the server. Bgcc1QfkP0UNgMZuHzi0hC1hA1SoVAyUrskmSkzRw3E= is the public key of the new default Chronicle server.
Previously, the default behavior of RemoteFetch was to check a Chronicle instance (i.e. the one at php-chronicle.pie-hosted.com), regardless of whethe
Previously, the default behavior of RemoteFetch was to check a Chronicle instance (i.e. the one at php-chronicle.pie-hosted.com), regardless of whether or not the bundle was already fetched and verified.
This was wasteful, and led to an accidental stress test of the Chronicle instance for the PHP community.
Now, the default behavior of RemoteFetch is to only query Chronicle instances on freshly-downloaded bundles, rather than every time getLatestBundle() is invoked.
We've already done a lot of work to ensure our server is stable even under the tremendous load we were seeing previously, but we do ask everyone to update to the latest version to improve the performance of your code that uses Certainty.
You can now specify an HTTP connection timeout for Chronicle queries and Github fetches.
Updated minimum version of sodium_compat to version 1.11.0
Updated minimum version of sodium_compat to version 1.11.0
Nothing published for this version
Per #25: We've made it substantially easier to specify a different Chronicle URL and Public Key in case the one we operate ever goes down.
Per #25: We've made it substantially easier to specify a different Chronicle URL and Public Key in case the one we operate ever goes down.
There is a table located at https://github.com/paragonie/certainty/blob/master/docs/README.md#php-chronicle-replicas-for-certainty which contains (currently only one) replica instances of the PHP Chronicle.
NEW: Trust Channels To better support Enterprise users that want to manage their own internal certificate authorities, we've marked each bundle with i
NEW: Trust Channels
To better support Enterprise users that want to manage their own internal certificate authorities, we've marked each bundle with its respective trust channel. Since our CA bundles come from Mozilla, the JSON file we provide is populated with "trust-channel": "Mozilla".
NEW: Composer Integration
You can now have Certainty request an up-to-date bundle at runtime by ensuring you add this entry to your composer.json file:
{
"scripts": {
"post-autoload-dump": [
"ParagonIE\\Certainty\\Composer::postAutoloadDump"
]
}
}
Then, you can simply use the local Fetch class instead of RemoteFetch in your application code. Every time you run composer update, it will fetch the latest bundles from Certainty.
This is a great way to reduce your runtime performance overhead while guaranteeing that you have the latest CACert bundle.
Note: You can create your own script that does the same thing. This is probably desirable if you'd like to put your configuration in a nonstandard location.
UPDATED: Psalm v2 will now be used on PHP 7 projects. This ensures we'll have better visibility into type safety issues as Psalm adds more checks over time.
FIXED: #22 Prevent infinite loops when trying to fetch newer bundles by using the locally installed CACert.pem bundles. Fix provided by @credomane.
Certainty now supports PHP 5.5+ projects in line with Guzzle 6's minimum version and the LTS version covered by many software projects we wish to inco
Nothing published for this version
Version 1.x is deprecated and we will not be providing noncommercial support. Please upgrade to v2 as soon as you can.
Version 1.x is deprecated and we will not be providing noncommercial support. Please upgrade to v2 as soon as you can.
Nothing published for this version
Fix #15 (Heisenbug) by using ParagonIE_Sodium_Compat instead of ParagonIE_Sodium_File.
ParagonIE_Sodium_Compat instead of ParagonIE_Sodium_File.CURLOPT_SSLVERSION.* Added cacert-2018-03-07.pem * Update sodium_compat to v1.6 * Update vimeo/psalm to v1.x * Fix psalm.xml configuration
Update bundle to 2018-01-17.pem.
Certainty's API is now stable, and we're confident in its ability to solve CA certificate issues for the PHP ecosystem.
Certainty's API is now stable, and we're confident in its ability to solve CA certificate issues for the PHP ecosystem.
Changes since 0.2.0:
LocalCACertBuilder to publish to configured Chronicles.This isn't just the second minor release of Certainty, it's the first release candidate for v1.0.0.
This isn't just the second minor release of Certainty, it's the first release candidate for v1.0.0.
Changes since v0.1.1:
RemoteFetch now verifies that fresh CA-Cert bundles have been logged into a Chronicle instance.Exception class.Like v0.1.0 but without a typo that breaks tests.
Like v0.1.0 but without a typo that breaks tests.
First semi-stable release of Certainty.
First semi-stable release of Certainty.
One column per quarter.