DIYgod/RSSHub

Choose this fork only if one of its added routes or removed behaviors is exactly what you want. For most adopters, upstream RSSHub is the safer choice because it is far more current, actively maintained, and likely to have broader route coverage and fewer compatibility surprises.

Choose this fork only if you want a narrowly curated organization-bulletin RSS service and can accept heavy divergence. For most adopters who want broad coverage or active upkeep, upstream RSSHub is the safer choice.

Prefer upstream unless you specifically need this fork's older Chinese-localized behavior or legacy route tweaks; otherwise the staleness and divergence are a material maintenance risk.

Choose this fork if you want a customized RSSHub with substantial route-level changes and you are prepared to own divergence. Choose upstream if you want the safest path to newer fixes, routes, and maintenance.

Choose this fork if you want a near-upstream RSSHub with modest maintenance changes and are comfortable carrying upstream backports yourself. Choose upstream if you want the broadest current route set and the fastest stream of fixes.

Prefer upstream unless you specifically need this fork's legacy customizations. This fork looks materially outdated and heavily diverged, so it is mainly attractive as a historical or niche customized baseline, not as a production starting point.

Prefer upstream unless you specifically want a frozen copy of RSSHub. This fork adds nothing visible, and its main downside is that it is materially behind current upstream work.

Choose this fork only if its route layout or documentation structure matches a specific need you already have. For most adopters, upstream RSSHub is the safer default because this fork is materially older and likely missing many recent fixes and routes.

Prefer this fork only if you need its custom route/discovery changes and can own maintenance. If you want broad, current RSSHub coverage with active upstream fixes, upstream is the safer choice.