Fanju6/NetProxy-Magisk: README-based editorial guide

Fanju6/NetProxy-Magisk describes itself in the README as "Based on the sing-box core, this Android proxy module supports one-click start/stop of transparent proxy and is designed for Android devices.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "项目简介", the README says: NetProxy 是面向已 Root Android 设备的系统级透明代理模块。模块以内置 sing-box 为代理核心，通过 cgroup 与 TC eBPF 接管系统及共享网络流量，并提供 Android 管理器、CLI 与 zashboard 三种管理入口。. That establishes the project's stated boundary, not a production test.

The README's "手写节点文件" section gives a useful starting point for deciding whether the project fits: 不要使用 direct、block、Proxy 或 Auto-Fastest 作为节点标签。. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: 不要使用 direct、block、Proxy 或 Auto-Fastest 作为节点标签。. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "管理入口". The source evidence includes: | 入口 | 适合场景 | |------|----------| | Android 管理器 | 日常使用，管理服务、节点、订阅、分应用代理、配置与日志 | | CLI | 终端操作、自动化和故障排查 | | Clash API + zashboard | 查看代理组、连接与延迟，进行运行时控制 |. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: README 没有给出可直接复制的安装命令。 When the README contains no runnable command, this article does not invent one. Open its "管理入口" section and confirm system dependencies, default ports, and first-run initialization before using a public server.