carbon-app/carbon

Choose this fork only if you want an older, customized Carbon variant and are prepared to maintain it yourself. If you want the full modern Carbon feature set, upstream is the better base.

Choose this fork only if its custom editor/UI changes matter more than staying current. If you want a maintained code-screenshot app with the broadest feature set, upstream is the safer default.

Choose this fork only if you want its custom email and UI flow and are willing to own a stale, significantly diverged codebase. If you want a current, broadly supported Carbon instance, upstream is the safer choice.

Choose this fork if you want a pared-down, local/offline Carbon variant and can live without upstream's sharing and UI features. Do not choose it if you want an actively maintained code-screenshot product or compatibility with Carbon's newer workflow.

Choose this fork only if you specifically want its older branded/customized Carbon variant. For most adopters, upstream is the safer choice because this fork is stale, significantly diverged, and has removed or fallen behind key capabilities.

Prefer upstream unless you specifically want this fork's older customization work and are willing to own maintenance. It is a poor choice for adopters who need current features, compatibility, or low-risk operation.

Choose this fork only if you want Carbon with custom embed, naming, and clipboard behavior and are willing to maintain a significantly divergent codebase. If you want the current upstream feature set and easier long-term maintenance, stick with upstream.

Choose this fork only if you want a customized, slimmer Carbon deployment and are willing to own the missing upstream features and merge debt. For most adopters, upstream is the safer default.

Choose this fork only if you want Carbon almost unchanged and are comfortable inheriting upstream work yourself. For most adopters, upstream is the better default because this fork is stale and does not show added capabilities.