AgniaSmirn/base_node
stale
significant_divergence
Selected Prefer upstream unless you need an archival copy; this fork adds no visible capability and is materially behind on maintenance and client support.
Adopt this fork only if the Docker publish workflow is the main thing you need. For running a current Base node, upstream is the better choice because this fork is far behind and shows no substantive node-side improvements.
killuamagic/node
stale
significant_divergence
Choose upstream unless you specifically need this older snapshot. This fork adds no visible capability, while upstream has continued active maintenance and feature work.
Elmer70849149/node
stale
significant_divergence
Prefer upstream `base/node` unless you specifically need an old snapshot. This fork adds no visible capabilities and is significantly behind, so adopters would mainly inherit stale behavior and miss recent node/client maintenance.
Prefer upstream unless you specifically need a frozen 2024 snapshot; this fork adds no visible features and is substantially behind on maintenance and compatibility.
CryptoKitty21/node
stale
significant_divergence
Prefer upstream base/node unless you specifically need a frozen 2024 snapshot; this fork adds no visible features and is materially behind on maintenance and client support.
CaseyKing11/node
stale
significant_divergence
Prefer upstream base/node unless you specifically need this older snapshot. This fork does not show added capabilities, and its age means it likely lags important node/client updates and fixes.
CryptoMonkey21/node
stale
significant_divergence
Prefer upstream unless you need this exact snapshot. This fork adds no visible capabilities, is materially behind current upstream maintenance, and is best treated as a stale baseline rather than a differentiated distribution.