Discofork
Repository brief

DIYgod/RSSHub

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:53:57.767Z
1mo ago

DIYgod/RSSHub

RSSHub is a large, active open-source RSS aggregation project for turning many kinds of online sources into RSS feeds. It has strong adoption (43,094 stars, 9,515 forks), is not archived, and was updated on 2026-03-30. Forks are most interesting if you want a widely used TypeScript/Node.js codebase with ongoing route additions, fixes, and deployment support across container, worker, and Vercel-style targets.

GitHub
Loading tags...
Stars43,094
Forks9,515
Default branchmaster
Last pushed2026-03-30T11:58:43Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose upstream unless you explicitly need this fork’s legacy customizations. For adopters, the main tradeoff is customization versus freshness: this fork appears materially behind and likely missing a large amount of current route coverage, fixes, and deployment support.

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.