# DiningFactory/panda-vpn-pro: a curated airport list repository, not a VPN > The repository is a Chinese-language README that tracks paid proxy subscription services (jichang) and the state of the censorship fight around them. It ships no client software, no nodes and no code, and its own title says the PandaVPNPro service it was named after has shut down. **DiningFactory/panda-vpn-pro** — 🚁🚀 2026机场推荐 | 熊猫VPN（PandaVPNPro）已确定跑路！快连VPN ，小牛加速器（小牛VPN）体验不佳且价格贵。低价机场，便宜机场，平价机场，性价比机场，高速机场，稳定机场，一元机场，翻墙机场，付费机场，收费机场，冷门机场，优质机场，廉价机场。机场评测，中国翻墙，科学上网，梯子。非永久免费梯子，官网，非永久免费VPN，非免费机场！VPN China。按量计费机场，按量付费机场，不限时机场。机场节点订阅，节点分享，Clash节点，V2ray节点，非免费节点。适用ClashForWindows，V2rayN，singbox，nekobox，小火箭等代理软件🚀🚁 - Repository: https://github.com/DiningFactory/panda-vpn-pro - Website: https://free-5620788.webadorsite.com/ - Stars: 15,601 · Forks: 405 - Language: Unknown - License: Apache-2.0 - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/diningfactory-panda-vpn-pro ## What DiningFactory/panda-vpn-pro actually is The name is misleading. This repository is not a VPN, not a client and not a fork of PandaVPNPro. It is a single README.md plus a LICENSE file, written in Chinese, that maintains a list of paid proxy subscription services, called jichang (airports) in that community, and a running log of events that affect them. The repository description opens by stating that PandaVPNPro has been confirmed to have absconded, and mentions Kuaikan VPN and Xiaoniu VPN as poor-value alternatives. So the project is named after a service it is warning you about. The audience is specific: Chinese-speaking users who already understand the difference between a VPN app and a subscription-based proxy service, and who want a second opinion before paying. The README is explicit that it is not a free VPN, not a free airport and not a permanent free tunnel. It is a buying guide with a news feed attached. One structural decision is worth noting. The README says the list will deliberately stop growing: the author states that keeping the number of recommended airports between 10 and 15, and never above 20, is better for timeliness than finding more of them. That is a defensible editorial position, and it is also a limit. If you want breadth, this is the wrong list. ## The notice log is the real product Most of the README is dated entries. They are the part that carries information you cannot get from a static recommendation list. The entries describe a sequence: entry-point block notifications becoming routine, some airports switching to burn-after-reading subscription links, others forcing an official client so no subscription URL exists at all, then a wave of line cuts, then most transit airports moving their entry points overseas. The README quantifies one consequence: prices up roughly 25 percent on average among the airports it recommends, with worse experience, including frequent node changes and subscription re-imports. The most recent entry, dated 2026.09.20, describes regional network blocking where all nodes time out and in severe cases local connectivity fails as well. The README's own recommended responses are to try mobile data instead of wifi, to change carrier, to add airports, or to wait. It calls the situation close to a dead end. That is unusually candid for a recommendation page, and it is the reason the log is more useful than the list itself. There is also a secondary notice section covering client software: Clash for Windows stopped updating, several Clash cores and GUIs were archived or deleted, and the README advises against continuing to use unmaintained proxy software. It notes that Clash Verge and Clash Verge Rev are different projects. Those entries are dated and specific, which is what makes them checkable. ## Install and first use: there is nothing to install This is the part where the repository differs from almost everything else on a code host. There is no package, no binary, no container image and no CLI. The top level contains LICENSE and README.md. The README does not document an installation procedure because there is no software to install. The only installation-adjacent instruction in the README concerns DNS, as a mitigation for node domain poisoning. It states that setting the proxy software's local DNS to a public resolver can reduce the effect, and gives two addresses: ```text 223.5.5.5 119.29.29.29 ``` If the proxy software does not support changing DNS, the README says to change the DNS on the device itself. It does not walk through that, and instead tells the reader to search for instructions for their proxy software, operating system or phone brand. That is the whole of the setup guidance the README offers. What you actually do with this repository is read it. The README gives one instruction it repeats three times in a single line: never pay annually. The reasoning given is that any airport can abscond, so a yearly plan concentrates your risk. That is the closest thing to a usage rule the project has. ## Where this repository fails you The first failure mode is temporal. A recommendation list about services that disappear is only as good as its last update, and the README itself acknowledges that a list that grows too large makes it impossible to notice a problem in time. The trade-off is stated openly, but it cuts against the reader: if an airport you already bought goes bad and it is not on the list, nothing here will tell you. The second is that the README is a single point of failure. It is one file maintained by one author, and the author notes that GitHub accounts were being banned and created a mirror site as a backup. If the repository becomes unreachable, the recommendation list and the notice log go with it. There is no data file, no feed and no machine-readable export you could archive yourself. The third is scope. The README covers proxy clients and airports for the Chinese censorship context. If you are outside that context, or if what you want is a conventional VPN with an app store listing, an account system and a support desk, this repository has nothing for you. It does not even host the software it tells you to use. Finally, the README's advice is not neutral. It recommends specific airports and tells readers when to avoid specific ones, and it does so without publishing a methodology for how an airport gets on or off the list. ## How it compares with a general proxy tool list The obvious alternative is a project like Clash Verge Rev, which is actual software: a GUI that consumes the subscription links these airports sell, runs the Mihomo core, and can be installed and updated. The difference in approach is fundamental. Clash Verge Rev solves the client problem, and its release notes and issue tracker tell you when it breaks. This repository solves the vendor-selection problem, and it has no releases and no issue tracker to consult. The two are complementary rather than competing, and the README treats them that way: it discusses Clash Verge Rev's uninstall bug in v2.3.1 and v2.3.2, which reportedly deleted Start menu entries, and notes the fix landed in v2.4.0. That is a client-side concern. The airport list is a supplier-side concern. If you only have time for one, pick the client. A working client with a mediocre subscription still connects; a great subscription with an unmaintained client is the situation the README warns about when it tells readers to stop using archived proxy software. ## Licence, maintenance and upgrade cost The repository is licensed Apache-2.0. That covers the repository contents, which are a README and a licence file. It says nothing about the airports, subscription services or client software the README discusses, and it grants no rights over any of them. Apache-2.0 also includes a patent grant and a warranty disclaimer, which is standard for a permissive licence and largely theoretical for a document repository. The maintenance picture is simple because there is no code. The last push was on 2026-09-20, one day before today's date, and the repository is not archived. The upgrade cost is therefore not a version migration but a re-read: the notice log is dated, and the useful entries are the recent ones. Older entries are kept, including a 2023 note on Clash for Windows and a 2024 note on account bans, so the file grows over time and the reader has to scan by date. There is a cost the README does not price: acting on the advice means buying subscriptions, and the README's central warning is that those purchases can be lost. The repository carries no liability for that, and the licence makes no representation about the accuracy of the list. ## Conclusion Adopt this repository only if you read Chinese and want a periodically updated reading list of paid proxy subscription services, with dated notices about which ones are unstable. Do not adopt it if you want a VPN app, an installer, or a client for iOS, Android or PC: the repository contains a README and a licence file, and no code. Before relying on anything in it, verify the current state of the specific airport you are considering on that airport's own site, because the README itself warns that any airport can disappear with your money. ## FAQ ### Is DiningFactory/panda-vpn-pro safe to use? The repository itself contains only a README and a licence file, so there is no software to run and no code to audit. The safety question applies to the airports it recommends, and the README states plainly that any airport can abscond and advises never paying annually for that reason. ### What are the top 3 best airports recommended by DiningFactory/panda-vpn-pro? The README does not rank airports or name a top three, and it says it deliberately keeps the recommended list between 10 and 15 to stay current. The search question behind this entry is about VPNs generally, not about this repository's list. ### Do I need to install anything to use DiningFactory/panda-vpn-pro? No. The repository has no package, binary, container image or CLI, and the README does not describe an installation procedure. You read the README and, separately, obtain a proxy client and an airport subscription of your own. ### Why does DiningFactory/panda-vpn-pro advise against paying annually? The README repeats the instruction not to pay yearly and gives the reason directly: any airport can disappear with the money. It notes that prices among its recommended airports rose roughly 25 percent on average after a wave of line cuts, which increases the amount at risk in a yearly plan. ### Which proxy clients does DiningFactory/panda-vpn-pro support? The repository ships no client, so it supports none. The README discusses client software that consumes airport subscriptions, including Clash, sing-box, v2rayN and NekoBox, and warns against continuing to use unmaintained clients such as Clash for Windows. ## Sources - [DiningFactory/panda-vpn-pro on GitHub](https://github.com/DiningFactory/panda-vpn-pro) - [Issues](https://github.com/DiningFactory/panda-vpn-pro/issues) - [License: Apache-2.0](https://github.com/DiningFactory/panda-vpn-pro/blob/main/LICENSE) - [Project website](https://free-5620788.webadorsite.com/) - [README](https://github.com/DiningFactory/panda-vpn-pro/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/diningfactory-panda-vpn-pro