Discofork
Repository brief

RSSNext/Folo

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-31T09:47:57.556Z
1mo ago

RSSNext/Folo

Folo (RSSNext/Folo) is an active, non-archived open source AI RSS reader with a large audience: 37,869 stars and 2,010 forks. It targets a multi-platform product stack and appears to be maintained actively, with recent commits on 2026-03-24 and ongoing repo updates. The repository is a TypeScript/Node.js monorepo under AGPL-3.0-only, with apps, packages, api, plugins, locales, and scripts.

GitHub
Loading tags...
Stars37,869
Forks2,010
Default branchdev
Last pushed2026-03-24T23:34:06Z
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 this fork if you need enterprise desktop packaging and fork-safe release automation. Avoid it if you want a close-to-upstream base with minimal maintenance, because it is materially behind current upstream.

Prefer upstream unless you specifically need an untouched older snapshot; this fork adds no clear product value and is materially behind.

Do not choose this fork for an actively maintained product base. It offers no added capabilities over upstream and misses years of upstream work, so the only defensible reason to adopt it is if you want a frozen archival copy.

Choose this fork only if you need its specific UI/desktop tweaks and are prepared to own maintenance. For most adopters, upstream Folo is the safer base because this fork is far behind and likely missing substantial recent work.

Choose this fork if your main need is Japanese localization with minimal functional drift; do not choose it if you need the latest upstream features, fixes, or broader product changes.

Choose upstream unless you specifically want this fork’s branding or ownership model. For most adopters, the 771-commit lag and lack of visible fork changes make upstream the safer, more current choice.

Choose this fork only if you want a personal snapshot and plan to own maintenance yourself. If you want the current Folo experience, upstream is the better base.

Prefer upstream unless you need an untouched old snapshot. This fork does not add capabilities, but it does lag far enough behind that it likely misses important fixes and ongoing product work.

Prefer this fork only if you want the small timeline and UI patches it adds and you are willing to maintain a very old base. For most adopters, upstream is the better choice because this fork is far behind and likely missing major fixes and features.

Choose this fork only if you want a near-identical copy of upstream Folo and intend to do your own maintenance. If you want the newest fixes or any fork-specific enhancements, upstream is the better default.