coolsnowwolf/lede

Choose this fork only if its board-specific patches or older release pin are the point. If you want an actively maintained base with current kernel, toolchain, and wireless work, upstream coolsnowwolf/lede is the better default.

Choose this fork only if its specific hardware patches or bundled packages match your target. For most adopters, the stale 2021 base and large divergence make upstream or a newer fork the safer default.

Prefer this fork if you want opinionated, device-specific build scaffolding and CI for the included routers. Prefer upstream if you care more about current OpenWrt/LEDE updates, wider platform coverage, or lower long-term merge cost.

Prefer upstream unless you explicitly need this fork's legacy patches or hardware-specific behavior; this fork looks like a frozen customization branch, not a good default base for new builds.

Choose this fork if you value its modem and device-specific additions more than freshness. Avoid it if you need an actively maintained, upstream-aligned OpenWrt base or broad platform compatibility.

Choose this fork if your priority is its bcm27xx/Raspberry Pi-specific downstream support and you are willing to live with substantial upstream lag and merge burden. Choose upstream if you want the newest OpenWrt work, broader maintenance, and lower long-term risk.

Choose this fork only if you need its exact legacy hardware or feature set. For most adopters, the active upstream is the safer default because this fork is old, highly diverged, and effectively stagnant.

Choose this fork only if you specifically want its older proxy-oriented firmware stack and are prepared to own the maintenance debt. For most adopters, upstream `coolsnowwolf/lede` is the better base because it is far more current and actively maintained.

Prefer this fork only if your hardware or deployment depends on its older, target-specific patches. If you want current upstream support, security updates, or lower maintenance risk, the main `coolsnowwolf/lede` tree is the better base.