hexojs/hexo

Prefer this fork only if you need its legacy, fork-specific behavior and can accept being far behind upstream. For new work or active maintenance, upstream Hexo is the safer choice.

Prefer upstream unless you explicitly need this older snapshot. This fork shows no functional additions, while it is behind upstream on recent fixes and maintenance work, so it offers little adoption advantage on its own.

Choose upstream unless you specifically need this exact older snapshot. This fork adds no visible capabilities and is already materially behind upstream, so it is a poor default choice for new adopters.

Prefer upstream Hexo unless you specifically need this frozen snapshot for compatibility or historical reasons.

Prefer upstream unless you specifically need the fork’s custom behavior and are prepared to maintain it. This fork looks like a legacy, highly customized branch with substantial drift and low recent activity, so it is a poor choice for new adopters who want current Hexo compatibility.

Choose this fork only if you need legacy behavior or existing fork-specific customizations; for new work or ongoing maintenance, upstream Hexo is the better default because this fork is stale and substantially behind.

Prefer upstream Hexo unless you specifically need this fork's legacy behavior or customizations. This fork is too stale and too far from upstream for most new adopters.

Prefer upstream Hexo for any active blog or plugin ecosystem use. Choose this fork only if you need its legacy behavior or already depend on its old custom features and are willing to accept major maintenance and compatibility risk.

Prefer this fork only if you want a near-upstream Hexo copy to own locally. If you want extra features or active fork maintenance, upstream Hexo is the better default.