/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

hashicorp/consul

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-30T15:55:02.904Z

1mo ago

hashicorp/consul

HashiCorp Consul is a large, active Go repository for service discovery, service mesh, API gateway, health checking, and dynamic application configuration across distributed infrastructure. It is not archived, has strong adoption signals, and is updated frequently, including recent security and feature work on March 30, 2026.

Loading tags...

Stars29,818

Forks4,581

Default branchmain

Last pushed2026-03-30T11:41:39Z

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 unless you specifically need this older customized baseline. This fork looks like a legacy maintenance branch with broader vendored integrations, not a healthy alternative for new Consul deployments.

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.

Fork comparison

Nmishin/consul

38/100

stale

significant_divergence

Prefer upstream unless you specifically need this older customized baseline. This fork looks like a legacy maintenance branch with broader vendored integrations, not a healthy alternative for new Consul deployments.

Likely purpose

To preserve or customize an older Consul codebase for a specific internal infrastructure environment, likely with stronger emphasis on vendor-pinned integrations and packaged deployment tooling than on tracking upstream feature velocity.

Best for

Teams that must keep an older Consul fork alive for legacy infrastructure.; Organizations with custom cloud/provider integrations already built around this snapshot.; Operators who prioritize stability of a frozen codebase over upstream feature parity.

Additional features

Large vendored dependency refreshes for AWS, Google Cloud, VMware vSphere, Kubernetes, and SoftLayer APIs suggest broader infrastructure integration support.
Changed release and packaging paths indicate the fork likely supports an older but customized build/deploy workflow.
Docs and Helm-related commit history suggests extra attention to operator documentation and Kubernetes installation workflows.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

It is 200 commits behind upstream and the last fork push was in 2019, so it likely misses years of Consul feature work, security fixes, and platform updates.
Upstream service mesh, API gateway, and health-check improvements from 2020-2026 are likely absent or incomplete here.
Recent upstream UI and security fixes are not reflected in this fork, making the browser UI and dependent tooling materially older.
The fork shows large deletions in UI assets and a removed/altered docs area, so some upstream UI/docs functionality appears reduced or harder to use.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

May be easier to keep stable in an environment that depends on the older vendored SDK set.
Could fit teams that need a frozen Consul baseline with custom provider integrations already wired in.
Likely preserves legacy operational behavior that some older clusters or automation expect.

Risks

Very stale relative to upstream, so security exposure and compatibility drift are high.
Massive divergence makes rebasing or cherry-picking upstream fixes expensive.
Users adopting it may inherit older APIs, older dependency versions, and reduced access to upstream documentation and UI improvements.