From ed833e80f6d90edc69847f926e52e241c16fc773 Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Mon, 11 May 2026 22:14:50 +0000 Subject: [PATCH] =?UTF-8?q?docs(readme):=20space=20out=20the=20Status=20bl?= =?UTF-8?q?ock=20=E2=80=94=20three=20separate=20blockquotes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 50cbac4..0d73aa6 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,11 @@ certctl is a self-hosted platform that automates the entire TLS certificate life The CA/Browser Forum's [Ballot SC-081v3](https://cabforum.org/2025/04/11/ballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods/) caps public TLS certificates at **200 days by March 2026**, **100 days by 2027**, and **47 days by 2029**. At 47-day lifespans, a team managing 100 certificates is processing 7+ renewals per week, every week, forever. Manual workflows stop being a choice. -> **Status: Early-access.** The certificate lifecycle core is production-quality, including [RBAC](docs/operator/rbac.md). v2.1.0 adds [OIDC SSO](docs/operator/oidc-runbooks/index.md), server-side sessions, and break-glass admin. Production welcome — [file issues](https://github.com/certctl-io/certctl/issues) when something's off, especially against your IdP. +> **Status: Early-access.** The certificate lifecycle core is production-quality, including [RBAC](docs/operator/rbac.md). + +> v2.1.0 adds [OIDC SSO](docs/operator/oidc-runbooks/index.md), server-side sessions, and break-glass admin. + +> Production welcome — [file issues](https://github.com/certctl-io/certctl/issues) when something's off, especially against your IdP. > **Actively maintained, shipping weekly.** [Open an issue](https://github.com/certctl-io/certctl/issues) if something breaks. CI runs the full test suite with race detection, static analysis, and vulnerability scanning on every commit.