chore: update Claude Code badge [skip ci]

This commit is contained in:
shankar0123
2026-03-30 19:30:54 +00:00
parent 46a58d518a
commit 207f2c6879
+1 -1
View File
@@ -12,7 +12,7 @@
[![GitHub Release](https://img.shields.io/github/v/release/shankar0123/certctl)](https://github.com/shankar0123/certctl/releases)
[![GitHub Stars](https://img.shields.io/github/stars/shankar0123/certctl?style=flat&logo=github)](https://github.com/shankar0123/certctl/stargazers)
<!-- CLAUDE_CODE_BADGE:START -->
[![Updated with Claude Code](https://img.shields.io/badge/Updated_with-Claude_Code_7f5efac_%28Mar%2030%2C%202026%2002%3A24%20PM%20CST%29-D97757?style=flat&logo=claude&logoColor=white)](https://claude.ai/code)
[![Updated with Claude Code](https://img.shields.io/badge/Updated_with-Claude_Code_1a91346_%28Mar%2030%2C%202026%2002%3A30%20PM%20CST%29-D97757?style=flat&logo=claude&logoColor=white)](https://claude.ai/code)
<!-- CLAUDE_CODE_BADGE:END -->
TLS certificate lifespans are shrinking fast. The CA/Browser Forum passed [Ballot SC-081v3](https://cabforum.org/2025/04/11/ballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods/) unanimously in April 2025, setting a phased reduction: **200 days** by March 2026, **100 days** by March 2027, and **47 days** by March 2029. Organizations managing dozens or hundreds of certificates can no longer rely on spreadsheets, calendar reminders, or manual renewal workflows. The math doesn't work — at 47-day lifespans, a team managing 100 certificates is processing 7+ renewals per week, every week, forever.