bitwalker/libcluster

This system is a distributed node clustering library that manages the discovery and connection of nodes across various topologies. It supports multiple clustering strategies, including DNS, Kubernetes, Gossip, and Erlang hosts, allowing for flexible service discovery and node management. The library provides comprehensive testing infrastructure and telemetry integration to ensure reliability and observability.

The library introduces several new clustering strategies to support different service discovery and node discovery mechanisms. Users can now use DNS-based discovery with \Cluster.Strategy.DNSPoll\ to periodically query DNS A/AAAA records. For Kubernetes environments, new strategies are available: \Cluster.Strategy.Kubernetes.DNS\ and \Cluster.Strategy.Kubernetes.DNSSRV\ for headless services, as well as the updated \Cluster.Strategy.Kubernetes\ which now supports multiple lookup modes (\:ip\, \:dns\, \:hostname\) and resource versions. Additionally, \Cluster.Strategy.ErlangHosts\ allows clustering via a \.hosts.erlang\ file, and \Cluster.Strategy.LocalEpmd\ discovers nodes on the local host. The existing \Cluster.Strategy.Epmd\ and \Cluster.Strategy.Gossip\ strategies have been refactored to use the new \Cluster.Strategy.State\ struct and support configuration via keyword lists, with Gossip now supporting optional encryption and broadcast-only modes.

lib/strategy · high confidence

The library has been refactored to support multiple topologies and custom distribution plumbing. Users must now configure \topologies\ (a list of named topologies) rather than a single \strategy\. Each topology can specify a \strategy\, \config\, and optional \connect\, \disconnect\, and \list\_nodes\ functions, allowing for greater flexibility in how nodes are discovered and connected. The \Cluster.Events\ module has been removed as it was redundant. Documentation and examples have been updated to reflect these changes.

(repo-wide) · high confidence

The library has been refactored to use a new \Cluster.Supervisor\ module that manages topology children directly, replacing the previous \Cluster.App\ and \Cluster.Events\ modules. Additionally, the \Cluster.Logger\ module has been updated to support compile-time purging and conditional logging based on a \:debug\ application environment variable, with \Logger.warn\ being used conditionally for compatibility with Elixir 1.11+.

lib · medium confidence

The file config/config.exs has been removed from the project. This file previously used Mix.Config to configure the libcluster application with the Epmd strategy. Its removal indicates a shift away from this specific configuration approach, likely as part of a larger refactoring or version update.

config · medium confidence

Added test suite for cluster strategies; Added test support infrastructure for HTTP mocking, cluster node management, and telemetry testing.

The project now requires Elixir 1.13 or higher (previously 1.3). Several dependencies have been updated: \dialyxir\ to \~\> 1.0 (from 0.3), \ex\_doc\ to \>= 0.0.0 (from 0.13), and \jason\ is now a dependency (replacing \poison\). Additionally, \telemetry\ and \exvcr\ have been added as dependencies.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 54 → 63 (+8.7)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 98 → 98 (-0.0)
• Architecture 100 → 100 (+0.0)
• Maturity 35 → 41 (+6.3)
• Readiness 50 → 67 (+16.9)
• Security 90 → 100 (+10.1)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — no supported dependency manifest was read
• Duplicated block (10 lines × 2) (lib/strategy/strategy.ex)
• Duplicated block (16 lines × 2) (lib/strategy/dns_poll.ex)
• Duplicated block (16 lines × 2) (lib/strategy/kubernetes_dns.ex)
• Duplicated block (17 lines × 2) (lib/strategy/dns_poll.ex)
• Duplicated block (17 lines × 3) (lib/strategy/kubernetes.ex)
• Duplicated block (21 lines × 2) (lib/strategy/kubernetes_dns.ex)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• No exposed public API
• Test reliability not included

• Duplicated block (12 lines × 2) (lib/strategy/strategy.ex)
• Duplicated block (13–17 lines × 4) (lib/strategy/kubernetes.ex)
• Duplicated block (14 lines × 2) (lib/strategy/dns_poll.ex)
• Duplicated block (15 lines × 4) (lib/strategy/kubernetes.ex)
• Duplicated block (16 lines × 2) (lib/strategy/dns_poll.ex)
• Duplicated block (21 lines × 2) (lib/strategy/kubernetes_dns.ex)
• Duplicated block (35–39 lines × 3) (lib/strategy/kubernetes.ex)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Hotspot: lib/strategy/kubernetes.ex (lib/strategy/kubernetes.ex)
• Members sharing a duplicated core (5 members, 50+ identical tokens) (lib/strategy/dns_poll.ex)
• No dependency advisory monitoring
• Outdated: dialyxir
• Outdated: ex_doc
• Outdated: exvcr
• Outdated: jason
• Outdated: telemetry
• TodoComment (lib/strategy/gossip.ex)
• TodoComment (lib/strategy/gossip.ex)
• …and 2 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

bitwalker/libcluster was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.