hashicorp/consul

Prefer this fork only if you must keep legacy customizations. For most adopters, upstream Consul is the better choice because this fork is stale, heavily diverged, and missing major newer capabilities and fixes.

Prefer this fork if you need Criteo-specific ACL templates and operational behavior that upstream does not provide. Prefer upstream if you value faster security updates, lower maintenance burden, and staying close to the mainline Consul release train.

Choose this fork if incremental KV fetches are the main requirement and you can tolerate being behind upstream. Choose upstream if you want the latest security fixes, API gateway work, and broader maintenance momentum.

Choose this fork only if you need its downstream-specific behavior and can absorb the maintenance burden. For most adopters, upstream Consul is the better default because it is far more current and actively maintained.

Prefer this fork only if you need its older custom behavior and are prepared to maintain a large upstream gap yourself. If you want current Consul features, security fixes, and lower maintenance risk, upstream is the better choice.

Prefer upstream unless you specifically need this old frozen branch or its local debug/customization work; otherwise the fork is too stale and too far behind to be a safe default.

Prefer upstream unless you explicitly need this fork’s frozen dependency set or legacy behavior. This fork looks materially stale and high-maintenance, so adopters should expect to inherit security, compatibility, and upgrade debt.

Prefer upstream unless you specifically need a frozen 2018-era fork. This fork is materially stale and diverged, so it is better suited to legacy pinning or experimentation than to production use.

Prefer the fork only if you need a frozen, legacy Consul variant with custom vendored integrations and can accept missing years of upstream fixes. For most adopters, active upstream Consul is the safer choice.