ClashX-V2Ray-TopFreeProxy merges third-party Clash feeds into one YAML and promises no working node

One merged YAML file stands in for seven upstream feeds

The README offers a combined subscription, a Clash YAML hosted at `combine/clash.config.yaml` on the main branch, plus a list of the individual sources it draws from. Seven feeds are listed between the `subscriptions:start` and `subscriptions:end` markers: Anaer, Ermaozi, Learnhard-cn, OpenRunner, Xrayfree, Zhuhai Free Nodes and Free18. Each is a raw URL to a YAML file, most of them hosted in someone else's GitHub repository, with Xrayfree served from xrayvip.com and OpenRunner from free.datiya.com.

The repository does not run any proxy server itself. It points a Clash client at files that other people publish. A separate item under Free Node Pool names Zu1k's proxypool releases and marks it with a star.

The practical effect is that the quality of the merged file depends entirely on those upstream publishers. The repository adds aggregation, not capacity. If a source disappears, the merged output loses its nodes, and the client you configured keeps pointing at the same combine URL.

A date-stamped OpenRunner URL breaks the day it rolls over

The OpenRunner entry in the current list is `https://free.datiya.com/uploads/20261102-clash.yaml`. The file name carries a date. The commented-out archive block at the bottom of the README shows why that matters: it holds a long run of the same host with consecutive dates, 20261010 through 20261101, each one a former entry.

So a person who copies the OpenRunner link directly into a client is pasting a URL that was replaced each day in the archive block. Copying the combined subscription avoids that, since the combine file is what the repository updates.

The archive block also holds older hosts and repositories that have since been dropped, among them clashnode.com, proxies.bihai.cf and several GitHub raw links. The README labels this block Archived Reference. It is a record of feeds that stopped being useful, and a reminder of how short-lived free subscription sources are.

Refresh runs every eight hours and keeps the old file when a pull looks bad

The Maintaining subscriptions section describes the pipeline. Sources live in `combine/sources.json`. From the repository root, with dependencies installed, two commands rebuild the output:

python -m combine.sources
python -m combine.refresh

Subscriptions refresh automatically every eight hours. The safeguard is specific: empty results, or a drop below half the published entry count, preserve both previous subscriptions. A broken upstream therefore cannot wipe the merged file in one run.

The dependencies are pinned in `requirements.txt`: `requests==2.34.2` and `PyYAML==6.0.2`.

The repository's last push was on 2 November 2026, and there are no GitHub releases. The code is a script and a data file, not a versioned package.

The health report checks sources, and the README says it does not test nodes

Two sentences in the README set the limit of what you can trust. First: check source health at `combine/health.md` for results. Second: node connectivity is not tested.

Those two statements describe different things. The health report tells you whether a feed returned entries. It cannot tell you whether any entry in the YAML will route your traffic. A feed can return many entries and every one of them can fail on your network.

The credits section adds a related caution: attribution does not imply every feed is currently usable. Ten projects and sites are thanked there, including NodeFree and Mfuu, which do not appear in the current subscription list. They are credited as current and historical providers.

If you try the combined link and see no working node, nothing in the repository promises otherwise. The README tells you to manually select a node if necessary, which is the closest it comes to guidance on a node that fails.

Setup is six clicks in ClashX, and the clients named are historical

The setup steps are written for ClashX on macOS. Open ClashX, click its icon in the status bar, choose Config and then Remote Config, click Manage and then Add, paste a subscription link into the url field, and press OK. A short video is linked beneath the steps.

The README then complicates its own tutorial. Under Installation it says that for a new installation you should use Clash Verge Rev, from the clash-verge-rev releases page, for Windows, macOS or Linux, and that the older clients and the setup steps that follow are retained as historical references. A bold line states that the original Clash repository has been deleted.

The older clients it lists are Clash for Windows, ClashX and ClashX Pro, the last with enhanced mode and native Apple Silicon support. Their download links go to third-party pages: the CFW page, WannaFlix and a wiki page called 糖糖のWIKI. The repository does not host those installers. For V2Ray users it links a separate `v2ray.md`, and there are Chinese-language versions of both tutorials, `clash中文版.md` and `v2ray中文版.md`.

The licence is undetected, and the disclaimer rules out commercial use

The repository carries a `LICENSE.md` file, yet the licence is reported as NOASSERTION, which means it was not matched to a standard open source licence. The README's Disclaimer explains the intent: the project is for personal, educational and noncommercial use only, and commercial use is prohibited. Noncommercial use, modification and redistribution are permitted under the terms in `LICENSE.md`, and third-party resources stay subject to their own terms.

That last clause has weight in this project. The subscription content belongs to other publishers, not to the repository, so the licence covers the repository's own files and does not grant rights over the feeds.

The disclaimer also asks you to follow relevant laws and regulations, and says the project owner is not responsible or liable in any manner for the use of the content. Whether and how a proxy may be used depends on where you are, and the README does not go further than that sentence.

A team that needs a clean, standard licence for redistribution should read `LICENSE.md` directly instead of relying on the label.

What a free shared subscription cannot guarantee

Several limits follow from how the repository works. It cannot promise that any node is online, since connectivity is not tested. It cannot promise stability, since one of the seven sources changes its URL daily. It cannot tell you who runs each node. The README names the publishers of the feeds, and it says nothing about who operates the servers behind the nodes inside them, or what those servers do with traffic.

That is the answer to the safety question people ask about Clash. The repository makes no safety claim of its own. The disclaimer disclaims liability, and the health report checks feed status only.

The repository also provides no client. Clash itself is a separate program, and the README notes the original repository has been deleted, so the client landscape is the fragile part of this setup. The README recommends Clash Verge Rev for new installs and keeps the older ClashX steps as history.

For V2Ray readers, the repository adds a tutorial file and nothing else: the merged subscription is a Clash YAML, and the V2Ray route is explained in `v2ray.md`.

Editorial conclusion

Use this repository if you already run a Clash client and want one merged subscription URL that a script rebuilds every eight hours from third-party feeds. Do not use it if you need nodes known to connect or a clear licence for reuse, because connectivity is explicitly not tested and the licence is not detected. Before pasting the combine URL into a client, open combine/health.md and see which sources currently return entries.

Frequently asked questions

Official sources

1. Issues
2. README
3. VPN-Subcription-Links/ClashX-V2Ray-TopFreeProxy on GitHub