caddyserver/caddy
This system is a modular, extensible HTTP server and reverse proxy that manages TLS certificates and acts as a PKI. It provides a comprehensive suite of HTTP handlers for routing, authentication, compression, and templating, alongside a flexible configuration system that supports both JSON and Caddyfile syntax. The architecture emphasizes pluggability, featuring a global eventing system, distributed session key management, and integrated monitoring via Prometheus metrics.
50.5
Adequate · 29 July 2026
61k
lines of production code
Go
primary language
3
bus factor · 723 authors in all
3
measurements over time
How it got here
2019 · Caddy v2 modular architecture
This period marks the development of Caddy v2, introducing a fully modular, pluggable architecture with a new Cobra-based CLI and a redesigned Caddyfile parser. The work focused on expanding the HTTP server capabilities with new handlers for templates, authentication, and request manipulation, while also adding robust TLS, logging, and compression features.
27 changes
2020–2022 · Native PKI and observability features
This period focused on expanding Caddy's capabilities as a full-featured web server and certificate authority. Key additions included a native PKI system for internal certificate management, an experimental event system for extensibility, and enhanced observability through Prometheus metrics and OpenTelemetry tracing. The work also introduced new HTTP handlers for server push, value mapping, and forward authentication, alongside significant improvements to the test suite.
15 changes
2023–2024 · filesystem abstraction and logging enhancements
This period focused on introducing a global filesystem registry to decouple file system access and enabling dynamic log field appending. It also added PROXY protocol support for listeners and an experimental response interception middleware.
8 changes
Survey your own repository
caddyserver/caddy was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 29 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit c96bca1269 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.