# shaoyouvip/free: a daily list of scraped proxy node subscriptions, and why the trust model is the whole story > This repository is not software but data: YAML, base64 and mihomo subscription files listing free proxy nodes collected from around the web and republished daily. This looks at what the files contain, how they are meant to be imported, and the risk a user takes on by trusting an endpoint it did not build. **shaoyouvip/free** — 周润发公益免费v2ray节点订阅、翻墙、免费翻墙、免费科学上网、免费节点、免费梯子、免费ss/v2ray/trojan节点、蓝灯、谷歌商店、翻墙梯子、v2ray节点、免费节点、免费v2ray节点、最新公益免费v2ray节点订阅地址、免费v2ray节点每日更新、免费v2ray/clash/singbox节点 - Repository: https://github.com/shaoyouvip/free - Website: https://blog.zrf.me - Stars: 1,323 · Forks: 100 - Language: Unknown - License: not declared - Published: 2026-10-19 · Updated: 2026-10-19 · Language: en - Canonical page: https://hysenlabs.com/projects/shaoyouvip-free ## A repository of data files, not a program The top level of this repository contains four files and a readme: `all.yaml`, `base64.txt`, `mihomo.yaml` and `GithubProxytest.txt`. That is the whole artefact, and it is worth being explicit about it, because a repository that looks like a project but is actually a data feed behaves differently. The three subscription files are the same content in three encodings. `all.yaml` is a YAML subscription, `base64.txt` is the same set in the base64 form that most clients expect for bulk import, and `mihomo.yaml` adds routing rules on top of the node list. The fourth file, `GithubProxytest.txt`, is a test file for GitHub proxy acceleration, which the release tag v1.0.0 also names, GitHub 代理加速测试专用. The primary language of the project is not recorded, the licence is not stated, and the repository publishes exactly one release. The last push was on 2026-10-15, and the readme carries a Star History badge, which tells you the traffic comes from people arriving through a search for free nodes rather than from a community filing issues. The homepage is blog.zrf.me, and the topics are the vocabulary of network circumvention: ss, ssr, trojan, v2ray, vmess, and the abbreviation for the censorship system itself. The readme states, in a single line, that all the free v2ray nodes are crawled from the network and should not be used for illegal purposes, and points to a Telegram channel for daily updates. ## Three subscription formats for three different clients The subscription URLs are published in two families, and the difference between them is not cosmetic. The first family is served from the project's own domain, and it is what the readme recommends for updating without a proxy: ```text https://d.zrfme.com/vless-all https://d.zrfme.com/vless-base64 https://d.zrfme.com/vless-mihomo ``` The second family is served straight from the repository on GitHub, as raw files: ```text https://raw.githubusercontent.com/shaoyouvip/free/refs/heads/main/all.yaml https://raw.githubusercontent.com/shaoyouvip/free/refs/heads/main/base64.txt https://raw.githubusercontent.com/shaoyouvip/free/main/mihomo.yaml ``` The distinction is about who can reach what. A user behind a restrictive network may not be able to fetch from raw.githubusercontent.com at all, which is the catch that the first family exists to solve: those URLs are reachable without a working proxy, so the list can be updated in the first place. The formats then differ by what the client has to understand. YAML is the plain subscription, base64 is the encoded blob that the Windows and Android clients bulk import, and the mihomo variant adds routing rules so that different traffic goes to different nodes rather than everything through the same one. The readme also has a section on importing nodes by hand, and it is more specific than most: for a base64 subscription you select all on the page, copy, then right-click the v2rayN taskbar icon and use the bulk import from clipboard option. And it carries a fix for the case where the paste does not work, namely to delete the trailing timestamp when copying, because a timestamp at the end of the copied text is what breaks the import. ## The client matrix is a compatibility list, not a recommendation The readme lists the clients it expects people to use, with the operating systems each one covers. SingBox is listed for Mac, Linux, Android and iOS, FlClash for Mac, Linux, Windows and Android, Clash Verge for Mac, Linux and Windows, Clash Meta Android and ClashX Meta for their respective platforms, V2RayN for Windows, V2RayNG for Android, and V2RayU for Mac. That table is the single most useful thing in the repository for an evaluator, because it is where the format question gets answered. A YAML subscription with routing rules is a mihomo format thing, so it applies to the Clash family and to the clients that speak it, whereas a plain base64 blob is what the V2Ray family imports. Choosing a subscription URL for a client that does not understand its format is the most common way this kind of list fails, and the readme's format table is the antidote. There is also a tutorial link for GUI for Clash, hosted on the same blog, which is a pointer to the more detailed guidance rather than documentation kept in the repository. The acknowledgements section names a contributor and links a Telegram channel for the daily updates, and the project carries a Powered by DartNode badge with a free VPS for open source offer, which is the hosting arrangement for the subscription endpoints. ## Where the trust problem actually lives Everything else about this repository is a detail, and this is the point. A free proxy node is a machine operated by a stranger, and when your traffic goes through it, that operator sees the destination and, unless the protocol is correct, the content. The readme says the nodes are crawled from the network, which is the honest phrasing: these are endpoints that other people published, gathered by a script and republished. Nobody vouches for them, nobody monitors them, and the operator of any given node may change tomorrow. That has two consequences for a user. The first is that using one of these nodes to carry a session cookie, an API token or a customer record hands it to a third party, and the fact that the client encrypts the transport to the node does not change the fact that the node is the endpoint. The second is that the list itself is a supply chain, and the fetching script that produces `all.yaml` is a crawler pointing at unknown addresses, which is the kind of thing that attracts abuse and gets nodes blocked. The readme's own instruction, 请勿用于非法用途, is the limit of what the project can offer. It is a note to the user, and it does not change what the endpoints are. None of that is a reason to refuse the repository, which is openly published and openly described. It is a reason to treat the artefact the way it is: a convenient, disposable, unverified supply of transport, useful for the case where a person needs to reach a website today, and not suitable for anything they would not paste into a public channel. ## Where this is the wrong tool Three limits are clear. The first is that there is no service here. No SLA, no support, no accountability, no uptime record, no update guarantee beyond the daily claim. A team that needs a proxy for production traffic needs a provider, not a scraped list, and the difference is not in the protocol but in whether anybody is answerable for it. The second is that the content is unverifiable by design. The files are regenerated by crawling, and the repository contains no test that a node works, no record of which node came from where, and no way to tell a healthy node from a hostile one. `GithubProxytest.txt` is a manual test artefact, not a continuous check. The third is the legal and regulatory surface, which varies enormously by country and by use. The readme's warning against illegal use is not a defence, and the topic list makes clear the intended use is circumvention of network restrictions, which some jurisdictions permit and others criminalise. That is a question for the person using it, and this article does not decide it. For anyone who needs a stable path, the alternatives are entirely different in kind: a commercial proxy service with a contract and a support desk, a self-hosted tunnel or VPN you control end to end, or a network that does not require circumvention at all. The difference is not the client, the format or the subscription URL, it is whether there is an entity behind the connection. ## Conclusion This repository fits a user in a network where ordinary package and app sources are blocked, who needs a working endpoint today rather than a service with a contract, and who understands that a free node is an unvetted third party. It does not fit anyone whose traffic carries credentials or work data, and it is the wrong place to look for a stable or accountable service. Before you subscribe, read the note in the readme about the nodes being crawled from the network, and treat every node on the list as hostile until proven otherwise, because the person running it can see everything you send through it. ## FAQ ### What is in the shaoyouvip/free repository? Three subscription files and a test file: all.yaml, a YAML subscription, base64.txt, the same node list in base64 form, mihomo.yaml, the same with routing rules, and GithubProxytest.txt for GitHub proxy acceleration testing. ### Which subscription URL should I use? The three at d.zrfme.com, for vless-all, vless-base64 and vless-mihomo, are the ones that can be fetched without an existing proxy. The three raw.githubusercontent.com URLs point at the same files in the repository, and the README presents them as the alternative. ### How do I import a base64 subscription into v2rayN? Select all on the page, copy, then right-click the v2rayN icon in the taskbar and use the bulk import from clipboard option. If the paste does not import correctly, the README suggests deleting the trailing timestamp when copying. ### Can I trust the nodes on this list? The README states that all the free v2ray nodes are crawled from the network, so they are unvetted third party endpoints. Whoever operates a node can observe the traffic that passes through it, so a node on the list should not carry sessions, tokens or anything you would not publish. ### Which clients are these subscriptions intended for? The README lists SingBox for Mac, Linux, Android and iOS, FlClash for Mac, Linux, Windows and Android, Clash Verge for Mac, Linux and Windows, Clash Meta Android and ClashX Meta for their platforms, and V2RayN for Windows, V2RayNG for Android and V2RayU for Mac. ## Sources - [Issues](https://github.com/shaoyouvip/free/issues) - [Project website](https://blog.zrf.me) - [README](https://github.com/shaoyouvip/free/blob/main/README.md) - [Releases](https://github.com/shaoyouvip/free/releases) - [shaoyouvip/free on GitHub](https://github.com/shaoyouvip/free) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/shaoyouvip-free