alibaba/etcd
stale
significant_divergence
Selected Choose this fork only if you need its legacy Alibaba-specific behavior and are prepared to maintain it yourself. For most adopters, current upstream etcd is the safer choice because this fork is stale and substantially behind.
microyahoo/etcd
stale
significant_divergence
Prefer this fork only if you want a heavily annotated, study-oriented etcd codebase. If you need a maintained, production-ready etcd, upstream is the better choice.
ozonru/etcd
stale
significant_divergence
Prefer this fork only if you need a frozen, heavily customized legacy etcd branch and are prepared to own the maintenance. For most adopters, upstream is the better choice because this fork is materially stale and far behind on fixes and reliability work.
skynetservices/etcd
stale
significant_divergence
Prefer upstream unless you are maintaining a legacy deployment that depends on this fork’s dashboard/discovery customizations. The fork looks materially stale and far behind modern etcd, so its value is mainly compatibility with old behavior, not a better current platform.
manafalbalushiboy/etcd
stale
significant_divergence
Prefer this fork only if you specifically want its robustness-testing and traffic-modeling work. For production etcd usage, upstream is the better default because this fork is stale and materially behind.
openshift/etcd
slowing
significant_divergence
Choose this fork if you need OpenShift-aligned operational workflows and downstream packaging/build integration. Choose upstream etcd if you want faster access to current fixes, less divergence, and a more general-purpose distribution.
irieg001/etcd
stale
significant_divergence
Prefer this fork only if you need its specific historical customizations and are willing to own a large, stale divergence. For almost everyone else, upstream etcd is the better choice because it is far more current, maintained, and operationally safer.
ssbostan/etcd
stale
significant_divergence
Choose this fork only if you specifically need its older local patches or legacy behavior. For most adopters, upstream etcd is the better choice because this fork is materially stale and heavily diverged.
k3s-io/etcd
stale
significant_divergence
Prefer this fork only if you specifically need the k3s-maintained snapshot and are comfortable absorbing upstream lag. Otherwise, upstream etcd is the better choice because this fork shows no added features and is substantially behind on fixes.
erikgrinaker/etcd
stale
significant_divergence
Prefer this fork only if you explicitly need its older customized behavior. For most adopters, upstream etcd is the better choice because this fork is materially stale and far behind current fixes and maintenance.