imputnet/cobalt

Choose upstream unless you specifically need this fork’s older branch state. It offers no visible added capability, while missing a meaningful slice of recent upstream work.

Prefer this fork only if you need its custom processing and frontend behavior and are prepared to own the maintenance cost. For most adopters, upstream cobalt is the safer default because it is active and materially ahead.

Choose this fork only if you need its older, specialized downloader behavior and are comfortable owning the maintenance burden. For most adopters, upstream is the safer choice because it is much newer, actively maintained, and likely to have better platform compatibility.

Prefer upstream unless you specifically need this fork's older, customized behavior or are prepared to own the maintenance. Choose the fork if you want a controlled baseline for local modifications; avoid it if you want current source support, active maintenance, and lower operational risk.

Choose upstream unless you specifically want this exact branch state. This fork offers no added capabilities, but its minimal divergence makes it easy to adopt as a base if you plan to customize cobalt yourself.

Choose this fork if you want a leaner, YouTube-oriented cobalt derivative and do not need the upstream web application. Stick with upstream if you value the full frontend, broader monorepo workflow, and lower divergence risk.

Choose this fork only if its added source support and frontend changes match your exact workflow and you are comfortable owning long-term maintenance. For general self-hosting, upstream cobalt is the safer choice because this fork is materially stale and likely missing newer fixes and platform support.

Choose this fork only if its older Twitter fixes or UI behavior are exactly what you want. For most adopters, active upstream cobalt is the safer choice because this fork is stale and materially behind on feature coverage and maintenance.

Prefer this fork if you want a more productized cobalt variant with extra workflows and are comfortable maintaining a large divergence from upstream. Prefer upstream if you want the simplest, best-supported media-downloader with fewer integration risks.