TryGhost/Ghost

Choose this fork only if its older Ghost baseline and custom content/editor tweaks are the point. If you want current Ghost features, security updates, or low-maintenance adoption, upstream is the better fit.

Choose this fork only if Chinese localization of an old Ghost version is the goal. For any production deployment or modern publishing workflow, upstream Ghost is the better fit because this fork is heavily outdated and substantially diverged.

Choose this fork only if you specifically want a legacy, heavily diverged Ghost snapshot with custom agent-workflow tooling. For anyone wanting a maintained CMS or production publishing platform, upstream Ghost is the clearly better choice.

Choose this fork only if ActivityPub/federated publishing is the reason you are adopting Ghost. If you want a stable, low-maintenance Ghost base, upstream is the safer choice because this fork is materially behind and highly divergent.

Prefer this fork only if you need its custom behavior and are prepared to maintain a large, outdated codebase yourself. For most adopters, upstream Ghost is the safer choice.

Choose this fork only if you explicitly want a customized, self-owned Ghost codebase and are prepared to maintain major divergence. If you want current Ghost capabilities, active fixes, and lower upgrade risk, upstream is the better default.

Prefer this fork only if you are committed to an old Ghost 1.x-era codebase. For new adoption, upstream Ghost is the better choice by a wide margin.

Prefer upstream unless you specifically need this older, heavily customized Ghost snapshot and its local developer workflows. The fork looks high-maintenance and materially behind current Ghost, so it is not a good default adoption target.

Prefer this fork only if you need its testing-oriented customizations and are prepared to own ongoing divergence. If you want a production Ghost base with straightforward upgrades, upstream is the safer choice.

Choose this fork if you want a customized Ghost deployment and can tolerate falling behind upstream. Avoid it if you need a low-risk, actively maintained base for frequent upgrades or long-term upstream compatibility.

Prefer this fork only if you want a near-upstream Ghost snapshot to customize yourself. If you want a maintained production base, upstream Ghost is the safer choice because this fork shows no added capabilities and is materially behind.

Choose this fork only if you need its custom admin, workflow, or operational changes. If you want the safest Ghost upgrade path, upstream is the better fit because this fork is stale and significantly diverged.

Prefer this fork only if you need its custom development workflow layer and are comfortable owning a stale, deeply divergent Ghost codebase. If you want current Ghost features, security, and release compatibility, upstream is the better choice.

Prefer upstream unless you specifically want the fork’s local tooling and workflow customizations. This fork looks more like an old, specialized developer sandbox than a maintained alternative distribution of Ghost.

Prefer upstream Ghost unless you specifically need this fork as a private mirror or starting point; it adds no visible functionality and is materially behind current upstream.

Choose this fork only if you need its custom workflow and are prepared to maintain a large delta from upstream Ghost. If you want the safest path, newest fixes, and lowest upgrade burden, upstream is the better default.

Prefer this fork only if the added federation/social-web direction is the goal. If you want a current, production-ready Ghost base, upstream is the safer choice because this fork is both stale and materially divergent.

Prefer upstream unless you specifically need this fork’s custom behavior and can own ongoing merges. This fork looks more like a private divergence than a maintained distribution, and the missing upstream delta is large enough to be a real adoption risk.

Prefer this fork only if you specifically need its federation-oriented changes and are prepared to do maintenance work. For most adopters, upstream Ghost is the safer choice because it is much more current and actively maintained.