Portfolio concentration
67%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
10 repositories updated in the last 90 days.
Leading language
Go
Portfolio mix
Go (20), HTML (2), Shell (2)
Average size
401
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
67%
of the visible star count comes from this organization's top three repositories.
401
stars per repository in this same snapshot.
Go
is the most common language here, with 10 repositories updated in the last 90 days.
Why this rank
This organization stands out because its public portfolio is relatively balanced across 30 repositories.
Organization pages work best when you separate portfolio breadth from flagship concentration. In Caddy's case, the visible top three repositories account for about 67% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Go (20), HTML (2), Shell (2). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | caddyserver/certmagic Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal | Go | 5.6K |
| 2 | caddyserver/xcaddy Build Caddy with plugins | Go | 1.5K |
| 3 | caddyserver/examples OBSOLETE. This repo was for Caddy v1. For v2 and newer, see our forum's wiki category. | CSS | 971 |
| 4 | caddyserver/ingress WIP Caddy 2 ingress controller for Kubernetes | Go | 820 |
| 5 | caddyserver/forwardproxy Forward proxy plugin for the Caddy web server | Go | 723 |
| 6 | caddyserver/caddy-docker Source for the official Caddy v2 Docker Image | Dockerfile | 566 |
| 7 | caddyserver/cache-handler Distributed HTTP caching module for Caddy | Go | 391 |
| 8 | caddyserver/nginx-adapter Run Caddy with your NGINX config | Go | 356 |
| 9 | caddyserver/website The Caddy website | HTML | 222 |
| 10 | caddyserver/replace-response Caddy module that performs replacements in response bodies | Go | 156 |
| 11 | caddyserver/dist Resources for packaging and distributing Caddy | Shell | 138 |
| 12 | caddyserver/gateway Kubernetes Gateway API implementation powered by Caddy | Go | 135 |
| 13 | caddyserver/vscode-caddyfile Rich Caddyfile support for Visual Studio Code | TypeScript | 118 |
| 14 | caddyserver/transform-encoder Log encoder module for custom log formats | Go | 115 |
| 15 | caddyserver/dnsproviders OBSOLETE: DNS providers adapted for use in Caddy to solve the ACME DNS challenge - for Caddy v1 only. See caddy-dns for v2. | Go | 99 |
| 16 | caddyserver/sublimetext Caddyfile syntax highlighting for Sublime Text 3 | 23 | |
| 17 | caddyserver/getcaddy.com Automated installer script for Caddy with plugins. DECOMISSIONED in 2020. | Shell | 23 |
| 18 | caddyserver/ntlm-transport NTLM reverse proxy transport module for Caddy | Go | 19 |
| 19 | caddyserver/zerossl ZeroSSL REST API client implementation for Go | Go | 13 |
| 20 | caddyserver/cue-adapter CUE config adapter for Caddy | Go | 13 |
| 21 | caddyserver/pkl-adapter Configure Caddy with Pkl format | Go | 11 |
| 22 | caddyserver/tree-sitter-caddyfile Caddyfile grammar for tree-sitter | JavaScript | 8 |
| 23 | caddyserver/moduledoc Automated JSON docs generation for Caddy modules | Go | 8 |
| 24 | caddyserver/caddy-railway Official Caddy template for Railway.com | HTML | 7 |
| 25 | caddyserver/json5-adapter JSON5 config adapter | Go | 6 |
| 26 | caddyserver/jsonc-adapter JSONC config adapter | Go | 5 |
| 27 | caddyserver/ingress-docker | 4 | |
| 28 | caddyserver/circuitbreaker A circuit-breaker module for the reverse proxy | Go | 4 |
| 29 | caddyserver/goversioninfo Golang Microsoft Windows File Properties/Version Info and Icon Resource Generator | Go | 1 |
| 30 | caddyserver/mutable-caddy | Go | 0 |
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.