Library / SDK
luestr/ProxyResource avatar
luestr/ProxyResource

luestr/ProxyResource: a Loon rule and plugin index maintained by one curator

Keli's Loon resource library: plugins, scripts and rules.

5,143 stars190 forksVim SnippetNOASSERTION

At a glance

What is it?
ProxyResource is not a proxy server. It is a Loon configuration index: templates, plugin entries and rules distributed through a Telegram channel and a plugin hub, licensed CC BY-NC-SA 4.0 with a 24-hour deletion clause. This review covers what the repository actually ships and where it stops.
Who is it for?
Adopt ProxyResource if you already run Loon on iOS or tvOS and want a curated starting point for a configuration file rather than assembling rules from scratch; the README itself says the repository is only an index and open-sources only the configuration templates. Do not adopt it if you are looking for a proxy server, a self-hosted gateway, or anything installable outside Loon, because the repository contains no runnable service and no release artifacts.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 18 days ago.
What is it written in?
Mainly Vim Snippet, 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

  • luestr/ProxyResource5,143 ★ · +196
Star history
Repository2026-09-232026-11-15
luestr/ProxyResource4.9k5.1k

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

Editorial analysis

What ProxyResource actually is, and who it is for

The name invites the wrong assumption. ProxyResource is not a proxy implementation, not a server, and not a library you import. The README states plainly that the repository is only an index and that only the configuration templates are open source. What it distributes is a set of Loon configuration templates plus pointers to plugin listings hosted elsewhere.

The intended reader is a Loon user on iOS or tvOS who needs a working configuration and does not want to hand-assemble one. Loon is a client-side proxy and rule engine for Apple platforms; a configuration file tells it which rules to apply and which plugins to load. ProxyResource supplies starting points for that file through a list of template badges that link to posts on t.me/ibilibili. There is also an English configuration example, which the README flags for English-speaking users.

If you are an engineer evaluating a networking component to deploy on a server, this repository is not in that category. The top level holds LICENSE, README.md, Resource/ and Tool/. There is no package manifest, no build file, and no service entry point.

The index model: templates in the repo, plugins on a hub

The architecture is deliberately thin. Two directories carry the weight. Resource/ is the other top-level directory, and Tool/ holds the Loon-related material, including a configuration diagram under Tool/Loon/Lcf/zh-CN/Resource/ConfigDiagram.png that the README recommends reading before configuring Loon features.

Plugins are not in the repository. The README's plugin section says to install them from 可莉的插件中心 at hub.kelee.one. That is the central design decision, and it has consequences. The repository stays small and the curator can update plugin listings without touching the index. In exchange, the repository is not self-contained: if the hub is unavailable, the plugin half of the offering is unavailable, and nothing in the Git history preserves it.

The configuration templates themselves are announced through Telegram post links rather than stored as named files in the README. Each badge points at a post on t.me/ibilibili. That means the README functions as a table of contents for a chat channel, not as documentation. Anyone cloning the repository gets the assets and the diagram, but the human-readable instructions live off-repo.

Installing a Loon configuration from this repository

There is no installer. The README gives no install command, no package name and no version, because nothing here executes on its own. What you install is a configuration file into Loon, on a device that already has Loon.

The first step is to read the configuration diagram the README points to, so you can configure Loon's features correctly. Then pick the template that matches your situation from the README's badge list. The badges are Telegram links to posts on t.me/ibilibili.

For plugins, the README does not give a file path at all. It says to go to the plugin hub at hub.kelee.one and install from there.

If the hub is unreachable, the plugin side of this repository is not usable at that moment, regardless of what the Git tree contains.

The README also tells English users to click the Config button, which is an example of the English Config of Loon. If your Loon interface is in English, start there rather than with the Chinese templates.

The licence is the sharpest constraint here

Two separate terms apply, and they pull in different directions. The README carries a CC BY-NC-SA 4.0 badge, and the repository includes a LICENSE file that the README links as LICENSE.md. That licence permits sharing and adaptation with attribution, for non-commercial use, under the same licence. It does not permit commercial use.

On top of the licence sits a caution block with conditions the licence itself does not impose. It states that the content is for study and research only, that it must not be used commercially or illegally, that it must not be redistributed on platforms inside mainland China, and that you must delete the content from your devices within 24 hours of downloading. It also asks users to report anyone publicly distributing or selling the content on Chinese platforms, and says that using the content counts as accepting these terms.

The 24-hour deletion requirement is incompatible with treating these templates as a long-lived configuration you keep on a device. That is not a legal opinion, and I am not giving one; it is a plain reading of the text the repository ships. If you need a configuration you can keep indefinitely and modify freely, the combination of non-commercial licensing plus a mandatory deletion window is a reason to look elsewhere. The README does not explain how the 24-hour clause interacts with the CC licence, and it does not offer an alternative licence for commercial users.

Where this breaks down

The dependency on a Telegram channel is the main failure mode. Every template badge in the README resolves to a post on t.me/ibilibili. If a post is deleted, the badge becomes a dead link and the template is gone from the reader's point of view, even though the repository is intact.

The second failure mode is scope confusion. ProxyResource has nothing to do with API Gateway, WiFi proxy settings, or corporate proxy configuration. It is a Loon-specific index. If you are troubleshooting an HTTP proxy setting on a laptop, this repository will not help and its README does not claim otherwise.

The third is maintenance shape. The last push was on 2026-10-28, so the index is current. But currency here means the curator is still posting; it does not mean the templates are versioned, tested against a specific Loon build, or accompanied by a changelog. The repository has no published GitHub releases, so there is no release history to diff against when a configuration stops behaving. You would be tracking a chat channel for changes, not a changelog.

What to use instead, depending on what you actually wanted

If you wanted a Loon configuration and you want it versioned with a changelog, the alternative is to maintain your own configuration file in your own repository and pull rules from upstream sources you control. The difference in approach is ownership: ProxyResource hands you a curated starting point and keeps updating it in a chat channel, while a self-maintained file costs you the assembly work but gives you diffs, rollback and a licence you choose.

If you wanted a proxy server rather than a client configuration, this repository is the wrong category entirely. Loon is a client; ProxyResource configures that client. Server-side proxy software is a separate field and the README does not discuss any of it.

If you wanted the rule sets themselves rather than the Loon-specific packaging, the general pattern in this space is to consume rule lists directly and write your own client configuration around them. That trades the curated template for control over which rules you apply and when they change. ProxyResource's value is precisely that someone else already made those choices for a Loon user; if you do not want someone else's choices, the index model has nothing to offer you.

Upgrade cost and what maintenance looks like

Upgrading is not a versioned operation. There are no releases, so there is no upgrade path in the usual sense. The templates are announced as Telegram posts and the plugin list lives on hub.kelee.one; both can change without any signal in the repository. The last push was on 2026-10-28, which tells you the index is being touched, but it does not tell you what changed or whether a template you adopted last month still matches the current post.

Practically, that means you should keep your own copy of whichever template you adopt, with the date you took it, so you can tell later whether the upstream version moved. The repository does not do that bookkeeping for you. It also does not document rollback, because there is no artifact to roll back to.

The licence cost is the other ongoing item. CC BY-NC-SA 4.0 requires attribution and share-alike, so if you adapt a template and share it, you carry those obligations forward. Combined with the README's non-commercial and no-mainland-China-redistribution conditions, the terms are narrower than a typical open source licence, and the repository does not offer a commercial track.

Editorial conclusion

Adopt ProxyResource if you already run Loon on iOS or tvOS and want a curated starting point for a configuration file rather than assembling rules from scratch; the README itself says the repository is only an index and open-sources only the configuration templates. Do not adopt it if you are looking for a proxy server, a self-hosted gateway, or anything installable outside Loon, because the repository contains no runnable service and no release artifacts. Before relying on it, verify three things: that the plugin hub at hub.kelee.one still resolves, that the Telegram posts behind each template badge are still reachable, and that the CC BY-NC-SA 4.0 terms plus the 24-hour deletion clause fit how you intend to use the files.

Frequently asked questions

Is luestr/ProxyResource a proxy server I can install?

No. The README states that the repository is only an index and that only the configuration templates are open source. It contains Loon configuration templates and assets, not a runnable proxy service.

How do I install the plugins listed by luestr/ProxyResource?

The README's plugin section directs users to 可莉的插件中心 at hub.kelee.one rather than to files in the repository. There is no install command for plugins in the README.

What licence does luestr/ProxyResource use?

The README carries a CC BY-NC-SA 4.0 badge and links a LICENSE file as LICENSE.md, which permits non-commercial sharing and adaptation with attribution and share-alike. The README also adds conditions about commercial use, redistribution in mainland China, and deleting downloaded content within 24 hours.

Does luestr/ProxyResource have versioned releases?

The repository has no published GitHub releases. Configuration templates are announced as posts on the t.me/ibilibili channel and plugins are listed on hub.kelee.one, so there is no release history to track changes against.

Official sources

  1. Issues
  2. luestr/ProxyResource on GitHub
  3. Project website
  4. 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/luestr-proxyresource.svg)](https://hysenlabs.com/projects/luestr-proxyresource)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/luestr-proxyresource.svg)](https://hysenlabs.com/projects/luestr-proxyresource)

Was this useful?