Discofork
Repository brief

chen08209/FlClash

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:32.509Z
1mo ago

chen08209/FlClash

FlClash is an active, multi-platform proxy client based on ClashMeta. It targets Android, Windows, macOS, and Linux, emphasizes simple use, open-source and ad-free distribution, and appears popular in its niche with 34,683 stars and 2,109 forks. The repo is still being updated, with recent commits through 2026-02-02 and a latest push on 2026-03-25.

GitHub
Loading tags...
Stars34,683
Forks2,109
Default branchmain
Last pushed2026-03-25T11:10:16Z
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

9 of 9 fork briefs
Selected

Choose this fork if you value the added desktop/UI work and platform-specific fixes more than staying perfectly current with upstream. Stick with upstream if you want the latest mainline changes and the lowest-maintenance path.

Prefer this fork if you want an Android-oriented FlClash build with bundled model handling, Firebase support, and a custom release pipeline. Prefer upstream if you want the most neutral multi-platform distribution and less package-level divergence.

Choose this fork if your priority is a maintained Android-centered FlClash with startup and VPN fixes. Stay with upstream if you need the broadest cross-platform release and build workflow coverage.

Choose this fork if you care about its build/release maintenance and LM-Firefly-specific project setup. Choose upstream if you want the freshest app behavior and the broadest compatibility with upstream Android integration.

Prefer this fork if you want Russian Windows packaging and a more opinionated deployment setup. Prefer upstream if you want the latest fixes, broader release support, and less risk from fork-specific defaults.

Choose this fork if you value the Android/Windows fixes and workflow additions more than staying current with upstream. Avoid it if you want the latest FlClash releases, broad compatibility, or lower maintenance risk.

Prefer this fork if you want a maintained FlClash build with privacy-oriented logging changes and practical platform fixes. Stick with upstream if you need maximum feature parity or depend on the removed system time check.

Choose this fork if you want upstream FlClash with targeted Windows/UI/release adjustments. Choose upstream if you value the fuller default documentation, release workflow, and a more standard out-of-the-box experience.

Prefer this fork if automatic network-based policy switching is the main feature you want; stick with upstream if you want the broadest, most conservative FlClash baseline.