Open-source project
ermaozi/get_subscribe avatar
ermaozi/get_subscribe

ermaozi/get_subscribe: a free proxy subscription collector whose own README tells you not to rely on it

Free airport/free VPN finder: automatically fetches free clash/v2ray/trojan/sr/ssr subscription links, continuously updated.

9,485 stars680 forksPythonGPL-3.0

At a glance

What is it?
ermaozi/get_subscribe is a Python project that publishes free Clash and V2Ray subscription links refreshed every 12 hours, and sorts nodes by whether a TCP connection succeeds. The maintainer's warnings are stronger than most of its features.
Who is it for?
Use it for a short test of a client setup or a temporary fallback, and nothing that matters. The README itself says free subscriptions are unsuitable for long-term use, warns creators away, and states that its connectivity check is not a speed or access test.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • ermaozi/get_subscribe9,485 ★ · +182
Star history
Repository2026-09-222026-11-15
ermaozi/get_subscribe9.3k9.5k

182 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two fixed subscription URLs that change contents every 12 hours

The project is not something you run to get a result. You point a client at a URL, and the contents behind it are refreshed every 12 hours. The README lists two links, one per client format. For Clash:

code
https://blog.ermao.net/sub/clash/ermao.net

And for V2Ray:

code
https://blog.ermao.net/sub/v2ray/ermao.net

The repository description says it automatically fetches free clash, v2ray, trojan, sr and ssr subscription links and keeps them updated. The practical consequence of a 12 hour refresh is that nodes you were using can disappear on the next update. A subscription you imported yesterday is a different list today, so a stable setup cannot be built on any single node from it. The repository has no GitHub releases, so the published links, not a tagged version, are the product.

The warning block comes before the links, and it rules out most uses

The first thing in the README is a warning section titled as important, placed above the subscription links. It says the free links are used by a large number of people at the same time, so they do not offer stable or safe conditions. It lists the usual problems of heavily shared nodes: polluted IP addresses, exits flagged by risk controls, fluctuating speed, and privacy that you cannot control.

It also addresses content creators directly. Short video makers, live streamers, self-media operators and e-commerce sellers are told not to use this kind of free subscription as a production network. The stated reason is that an IP with a bad history can trigger platform throttling, account anomalies or stronger login verification.

The links come from the internet, the README says, and are for learning and testing only, with a reminder to follow local law.

A TCP handshake is the only thing the connectivity check proves

After each automatic collection, the project keeps the full set of subscriptions under subscribe/ and generates three more directories, each containing clash.yml and v2ray.txt. subscribe/reachable/ holds nodes to which the machine running the job could open a TCP connection. subscribe/unreachable/ holds nodes where the TCP connection or the DNS resolution failed. subscribe/untested/ holds UDP or QUIC protocol nodes, nodes whose address could not be resolved, and non-public addresses, none of which are judged unusable.

The README is explicit about the limit. This is not proxy authentication, not an egress access test and not a speed test. A node that connects is not necessarily a working proxy, and a failure may only reflect restrictions on the network of the machine that ran the check. So the reachable list is a filter against dead hosts, not a guarantee.

Protocols the check skips end up in a pile nobody validates

The untested category matters more than its name suggests. Any node that uses UDP or QUIC cannot be checked with a TCP connection, so it lands in subscribe/untested/ along with unresolvable and non-public addresses. The README says these are not declared unusable, only not classified.

If your client relies on a QUIC based protocol, the reachable list will simply not contain your nodes, and the unreachable list will not either. You are left with an unsorted folder and no signal at all about which entries work. The tooling gives you no second stage that tests those nodes by another method.

The classified subscriptions are also published online. Replacing clash with v2ray in a link gives the other format. Links exist for TCP reachable nodes, for failed nodes and for untested nodes, and a health report in JSON stores the check time and the number of nodes in each category.

Slow at peak hours is the maintainer's own description of the experience

The README includes a section about real use, and its description is modest: during off-peak hours you can watch video, while at peak hours there may be some stuttering. That is the only performance statement in the project, and it is qualitative. There are no measured speeds, no node counts and no uptime figures anywhere in the README.

The maintainer's FAQ goes further. Asked whether a free airport is suitable for long-term use, it answers that it is not: free subscriptions suit temporary tests or short emergencies, and a long-term user is advised to pick a paid service with a stable reputation. Asked why creators are discouraged, it points to shared exit IPs with complicated histories, which are more likely to hit platform risk controls and cause throttled content or abnormal logins.

Client help covers Android, Windows and iOS, and the paid list is the exit door

Setup tutorials are linked for three platforms only: Android, Windows and iOS, each pointing to an article on blog.ermao.net. The README names no macOS or Linux tutorial, so users of those systems have to work out client configuration for themselves.

For people who find the free links unsatisfactory, the README points to a separate page of cheaper paid providers that the maintainer has collected, at https://blog.ermao.net/posts/vpn. There is also a Telegram discussion group, @fanqiangjiaoliu.

All of this places the project in a specific role. It is a funnel and a free sample, and the maintainer's own advice for anything lasting is to leave it. The homepage is https://www.ermao.net.

A small Python repository with pinned dependencies and a GPL-3.0 license

The top level contains check_nodes.py, get_projaec_info.py, main.py, requirements.txt, and the directories log/, mail/, subscribe/, tests/ and worker/, along with .github/, LICENSE and README.md. The requirements file pins four packages: requests==2.34.2, matplotlib==3.10.9, pandas==2.3.3 and PyYAML==6.0.3.

Pinned versions are good for reproducing the job but mean you must update them yourself if you fork. The code is licensed GPL-3.0, so a fork that you distribute carries the same license obligations. The repository is not archived and the last push was on 2026-11-01.

A tests/ directory exists, but the README says nothing about running it, and the files in the subscribe/ directory are produced by the automatic collection rather than written by hand.

Editorial conclusion

Use it for a short test of a client setup or a temporary fallback, and nothing that matters. The README itself says free subscriptions are unsuitable for long-term use, warns creators away, and states that its connectivity check is not a speed or access test. Before importing a link, assume the exit is shared with many other users and keep any account you care about off it.

Frequently asked questions

Which subscription is free in ermaozi/get_subscribe?

The README lists a free Clash subscription link and a free V2Ray subscription link, both refreshed every 12 hours. They are shared with many users and are meant for learning and testing.

Do I have to pay to use ermaozi/get_subscribe?

No, the subscription links are free. The README says free subscriptions suit temporary tests, and it links a page of cheaper paid providers for anyone who needs something longer lasting.

How do I find the subscribe links in ermaozi/get_subscribe?

They are in the README: https://blog.ermao.net/sub/clash/ermao.net for Clash and https://blog.ermao.net/sub/v2ray/ermao.net for V2Ray. Full collected sets are also kept under subscribe/ in the repository.

Official sources

  1. ermaozi/get_subscribe on GitHub
  2. Issues
  3. License: GPL-3.0
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/ermaozi-get-subscribe.svg)](https://hysenlabs.com/projects/ermaozi-get-subscribe)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/ermaozi-get-subscribe.svg)](https://hysenlabs.com/projects/ermaozi-get-subscribe)

Was this useful?