A warehouse for people who already know their proxy client
ios_rule_script is less a conventional application than a large distribution point for routing rules, rewrite rules, and automation scripts. Its own description says the project does not produce the rules so much as collect them from open-source sources around the internet. That distinction matters: convenience is the product, while trust and compatibility remain the user's responsibility. The supplied README is primarily Chinese, and no English guide is evident there.
The scale is the immediate attraction. The repository has 27,862 stars, contains 11,226 files in our checkout, and was pushed on 2026-09-13, the day of this review. It gathers material that would otherwise be scattered across projects and presents dedicated directories for traffic splitting, request rewriting, scripts, and external resources. For experienced users, one familiar source can be easier to monitor than many unrelated subscriptions.
The catalog is broad, but the README expects prior knowledge
The README points directly to the rule and rewrite trees, then lists task-specific scripts. Examples include retrying Baidu Tieba check-ins, removing locally cached app startup ads, running daily check-ins for several Chinese services, sending jobs to Synology Download Station, and watching Apple Store inventory. A Quantumult X gallery and a BoxJS subscription provide practical entry points instead of forcing every item to be copied by hand.
There are 10 scripts in the supplied table. Nine are marked as maintained normally, while the Apple Store inventory watcher is marked paused. The frameworks are identified as MagicJS 2 or MagicJS 3, which is valuable compatibility information, but the table is still a catalog rather than a complete setup tutorial. You need to understand the host client, permissions, request interception, and account data each script may require.
That focus is a strength when the reader already knows the ecosystem. The project does not bury its useful assets behind a custom dashboard or service. Raw files, directory links, the gallery, and the subscription can fit into existing client workflows. The separation between rules, rewrites, scripts, and external material also gives reviewers a reasonable starting point for deciding what should enter a configuration.
The legal and operational warnings are unusually prominent. The README says the contents are for learning and research, tells users to remove them within 24 hours, disclaims accuracy and legality, and restricts reposting by public accounts or media. Those statements deserve review alongside the GPL-2.0 repository license, especially for an organization considering redistribution. They also reinforce that inclusion in this collection is not a quality guarantee.
What happened when we ran it
Our run examined commit 5f74cf1 in a fresh, unprivileged Debian container with 3 CPUs and 8 GB of RAM. The measured project was the Python component at ./script/zheye/server/, even though GitHub labels the overall repository JavaScript. Installation succeeded in 14 seconds: 35 packages were installed and occupied 37 MB. The build then succeeded in 2 seconds.
There was no test script or target, so the test stage was skipped. That is not the same as a passing suite. pip-audit found 0 known vulnerabilities in the installed Python dependencies, which is reassuring but narrow evidence. We also found 0 CI workflow files, no Dockerfile, and no tests directory. The checkout occupied 529.3 MB and contained about 10,394 lines of source.
These results show that one server subproject can be installed and built quickly on our box. They do not prove that thousands of routing and rewrite files are syntactically valid in every supported client, that remote endpoints still behave as assumed, or that account-facing scripts are safe for unattended use. With no repository-level automated test signal, users should validate only the selected rules in a disposable profile before moving them into daily traffic.
Activity is strong, release discipline is weak
The project is plainly active by one useful measure: its last push was 2026-09-13. Adoption is also substantial at 27,862 stars. Against that, 379 open issues represent a large support and triage surface, and the provided data lists no latest release. A missing release is not evidence of abandonment here, because the same-day push shows ongoing work, but it does remove a convenient stable checkpoint for cautious users.
The README says external resources are integrations and backups, and directs questions about them to their original authors. That boundary is honest, yet it fragments support across upstream projects. Before subscribing to updates, inspect issue activity for the exact rule family you plan to use, pin a reviewed commit such as 5f74cf1 when reproducibility matters, and keep a rollback copy of the last working client configuration.
It belongs at the configuration edge, not at the center of a stack
In a real setup, ios_rule_script should feed a controlled staging step. Select the smallest relevant rule or script, read its local documentation, inspect the source and destinations, test it in the intended client, and only then add it to a production profile. Treat remote subscriptions as changing inputs. A bad rewrite or stale domain rule can affect traffic even when the repository itself installs cleanly in 14 seconds.
Choose Loyalsoldier/v2ray-rules-dat when the requirement is generated V2Ray geosite and geoip data, or ACL4SSR/ACL4SSR when Clash-oriented ACL configuration is the priority. ios_rule_script is the stronger fit when Quantumult X galleries, BoxJS subscriptions, MagicJS 2 or 3 scripts, and a mixed collection of rules and rewrites are exactly what you need. Its breadth saves discovery time, but it does not replace client expertise, source review, or your own validation gate.