/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

caddyserver/caddy

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T20:00:18.486Z

1mo ago

caddyserver/caddy

Caddy is a large, actively maintained Go-based web server project focused on fast, extensible HTTP/1-2-3 serving with automatic HTTPS. It has a strong upstream signal for fork interest: 71,180 stars, 4,691 forks, and very recent commits as of 2026-03-30.

Loading tags...

Stars71,180

Forks4,691

Default branchmaster

Last pushed2026-03-30T16:56:10Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream Caddy unless you specifically need this fork's legacy naming and packaging behavior. This fork looks like a stale, highly divergent rebrand with limited evidence of ongoing feature development.

Choose this fork if you want a specialized, CoreDNS-aligned Caddy base and can live without parts of upstream’s broader web-server feature set. Choose upstream if you need the full, actively evolving Caddy platform with minimal compatibility risk.

Choose this fork only if h2c reverse proxy support is the deciding requirement. Otherwise, upstream Caddy is the safer default because it is active, much newer, and far less likely to surprise you with missing fixes or compatibility drift.

Choose this fork only if you need its specific behavior and can absorb maintenance debt. For most adopters, upstream Caddy is the safer default because this fork is stale, significantly diverged, and appears to have removed or frozen some upstream capabilities.

Prefer this fork only if you already depend on its older semantics or specific backported proxy/TLS changes. For most adopters, upstream Caddy is the better choice because this fork is stale, materially diverged, and missing modern features such as ECH and recent maintenance work.

Choose the upstream Caddy project unless you specifically need this fork's customized behavior. This fork looks like a long-stalled, heavily diverged variant with likely feature loss and meaningful maintenance risk, so it is best only for adopters who already rely on its bespoke changes and can own ongoing maintenance.

Prefer upstream unless you specifically need this older pinned state; the fork offers no visible enhancements and is materially behind active Caddy development.

Prefer this fork only if you need legacy Caddy behavior and can accept major divergence from upstream. For most adopters, the active upstream is the safer and more capable choice.

Choose this fork only if you need its specific downstream behavior and are willing to own the divergence. If you want the newest Caddy features, fixes, and the broadest compatibility with upstream docs and modules, upstream is the safer default.

Prefer the upstream Caddy unless you specifically need the fork's custom reverse-proxy/TLS behavior and are willing to own the maintenance debt. This fork is materially stale and highly diverged, so it is best treated as a specialized legacy branch, not a general-purpose replacement.

Fork comparison

WedgeServer/wedge

38/100

stale

significant_divergence

Prefer upstream Caddy unless you specifically need this fork's legacy naming and packaging behavior. This fork looks like a stale, highly divergent rebrand with limited evidence of ongoing feature development.

Likely purpose

A downstream-maintained fork for users who wanted an early Caddy-based server under different binary/config names and fork-specific build or distribution behavior, not a current upstream-compatible Caddy experience.

Best for

Users deliberately maintaining an old Caddy-based fork with custom naming or packaging requirements.; Teams that need a frozen legacy server codebase and do not want upstream churn.; Maintainers willing to own long-term divergence and backport security fixes themselves.

Additional features

Fork-specific binary and config naming plus updated help text.
Custom build-script behavior for building multiple targets at once.
Fork-specific CI, issue-template, and release workflow changes.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

It is far behind upstream, so it likely misses many years of Caddy fixes and features, including the modern HTTP/3-focused stack and current automatic-HTTPS behavior.
It appears to have removed or reduced direct Caddy branding and references, which makes upstream documentation and ecosystem guidance harder to apply unchanged.
Because the fork is stale and highly divergent, upstream plugin/module compatibility and maintenance cadence are likely much weaker than in current Caddy.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream operational features such as auth, admin, or session handling may be reduced or absent.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Could suit teams that need the fork's renamed binary/config conventions.
May be easier to adopt if you want a frozen older codebase with fork-specific packaging.
Large change set suggests it was customized for a particular downstream distribution or deployment workflow.

Risks

Very stale: last push was in 2017, so security fixes and bug fixes from upstream are likely missing.
Huge divergence and vendored changes make future rebases or merges expensive.
Upstream docs, plugins, and troubleshooting guidance may not match this fork well.
The fork's product direction is unclear from the metadata alone, which raises adoption risk.

caddyserver/caddy · Discofork