# NiREvil/vless: V2Ray Subscriptions and Rust Scanners > NiREvil/vless collects V2Ray subscription links, configuration files, and Rust network scanners. It suits users familiar with V2Ray clients and Cloudflare deployments, not people seeking a self-contained VPN client. **NiREvil/vless** — v2ray subscription links - Repository: https://github.com/NiREvil/vless - Stars: 1,356 · Forks: 352 - Language: Rust - License: GPL-3.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/nirevil-vless ## What NiREvil/vless Contains NiREvil/vless addresses the practical problem of finding, distributing, and importing V2Ray connection information. Its intended users are operators and individuals who already work with VLESS, subscription URLs, WARP, Shadowsocks, Trojan, and clients such as v2rayNG or Hiddify. It does not present itself as a proxy client or a managed VPN service. The repository layout contains several kinds of resources. `sub/` holds subscription-related files, while `edge/`, `DNS over HTTPS/`, `warp.json`, `Cloudflare-IPs.json`, and `sing-box.json` indicate a wider collection of networking resources and configuration files. Repository topics include `amnezia`, `clash-meta`, `cloudflare-workers`, `fragments`, `free-dns`, `mahsang`, `serverless`, `shadowsocks`, `trojan`, `v2ray`, `vless-ws-tls`, and `warp`. The README does not define a single manifest that explains how all of these components are generated or related. This distinction matters for adoption. A repository of subscription data is not the same as a maintained VPN account, and a file that imports successfully is not evidence that its endpoint remains reachable. Users need a compatible client and a process for checking the current contents of `sub/`. NiREvil/vless is better understood as a collection point for connection information and related network resources than as a finished application. ## How Subscription Data Reaches v2rayNG and Hiddify The documented subscription flow starts outside NiREvil/vless. A BPB panel can be created through the BPB Wizard, after which its normal subscription URL is added to v2rayNG or Hiddify. The README also says that `edge/assets/BPB-settings.dat` can be uploaded through the BPB panel to apply repository settings and several addresses. Once imported, the client retrieves the remote subscription data, interprets the contained entries, and makes them available for selection. NiREvil/vless organizes or supplies the configuration source, but the README attributes the import and URL Test operations to the client. This is the important architectural boundary: the repository is a data and tooling layer, not the TCP, TLS, and routing implementation used for an ordinary connection. The README recommends running URL Test after import. It states that some entries ping and mentions tests with Abrau, Shatel, Hamrah, MCI, and Asiatek. Those statements describe the README author's reported experience. The README does not publish a test date, endpoint inventory, success rate, latency table, or automated freshness check. Readers should use URL Test for their own current network and should not interpret an imported entry as guaranteed to work. A separate test is still needed when changing client, provider, location, DNS settings, or network. ## RScanner, CFScanner, and Repository Tooling The Rust package is named `RScanner`, version `0.2.0`, and uses edition `2021`. `Cargo.toml` declares two executables. `RScanner` is compiled from `edge/proxies-main.rs`, while `CFScanner` is compiled from `edge/cf-scanner.rs`. Their names indicate that the repository includes tools for scanning proxies and Cloudflare-related addresses, but the README gives no command examples for either binary. The Rust dependencies support concurrent network work and structured input. They include `tokio`, `reqwest`, `clap`, `serde`, `serde_json`, `native-tls`, and `tokio-native-tls`. Other declared packages include `rand`, `anyhow`, `futures`, `colored`, `chrono`, and `chrono-tz`. Based on this manifest, the binaries are expected to parse command-line input, perform network requests, and handle JSON data. It would be incorrect to invent specific flags, target ports, scan limits, output fields, or completion conditions because the README does not define them. The repository also contains `package.json`, `package-lock.json`, ESLint configuration, and Python formatting configuration. Its Node.js requirement is `^20.19.0 || ^22.13.0 || >=24.0.0`. Development scripts include formatting and linting operations. This is repository maintenance tooling, not a documented npm application for retrieving VLESS connections. The README does not explain the relationship between the Rust scanners and the JavaScript or Python checks. The `boringtun-boringtun-cli-0.5.2/` directory is also listed, but its integration with the Cargo binaries is not explained. ## Installing the External BPB Wizard Workflow NiREvil/vless does not document installation commands for compiling `RScanner` or `CFScanner`. Its BPB section points readers to the separate Wizard at `http://Wizard.bpb-panel.workers.dev`. The following command is the installation command printed in the README for that external workflow. It requires Bash, `curl`, network access, and an existing or newly created Cloudflare account. ```bash bash <(curl -fsSL https://raw.githubusercontent.com/bia-pain-bache/BPB-Wizard/main/install.sh) ``` The wizard first asks whether to create a new panel or modify an existing one. For a new panel, select option `1`. It then asks for Cloudflare authentication and access permission. The browser authorization flow belongs to the external BPB Wizard, so the reader should expect to return to the terminal after granting the requested access. The next choice is between Workers and Pages deployment. The README recommends Workers because it permits use of port 80 without TLS in the conditions discussed by the author. Select `1` for Workers or `2` for Pages. The wizard also generates or requests a subdomain and UUID. Press Enter to retain its generated value, or enter a custom subdomain containing lowercase English letters and numbers without spaces, commas, or periods. ## Creating and Testing a First Panel After the wizard finishes deployment, open the BPB panel. The README says that the operator can upload `edge/assets/BPB-settings.dat` through the panel's settings-related import option. The panel then provides a normal subscription link. Add that link to v2rayNG or Hiddify, but do not confuse uploading a settings file with creating a server. The README does not state that NiREvil/vless operates the deployed BPB panel. In the client, locate the subscription import function, add the normal subscription link, and then run URL Test. The README names v2rayNG and Hiddify but does not give complete menu sequences for their current interfaces. Exact labels can change between client versions, which makes subscription import and URL Test the reliable actions documented here. The client should show imported entries after a successful subscription response. URL Test then attempts the endpoints and displays the client's own result. If no entries appear, check the subscription response in the client. If entries appear but fail, the likely boundary is endpoint availability, configuration compatibility, or current network conditions. The README does not define a repair, rollback, or endpoint retirement procedure for either case. Users who need such guarantees need a directly managed server rather than a shared collection of remote links. ## Deployment Limits and Alternative Architectures The BPB panel is an external service arrangement, and the README says the Cloudflare account needs email verification and authorization. It recommends Workers over Pages for the network conditions discussed by the author. That recommendation is not a guarantee about privacy, availability, traffic handling, or terms of service. The README does not reproduce the BPB Wizard project's own operational and security documentation. The separate Katabump Free Hy2 section documents a recurring dependency. Its server must be renewed through the site dashboard every four days or it may stop working. That makes the free instance unsuitable for unattended operation. The Psiphon section describes an emergency option and warns that its bandwidth and IP quality are poor for normal use. These limitations apply to those recommendations, not automatically to every endpoint represented elsewhere in the repository. A real alternative is a directly managed sing-box or V2Ray server. The operator would provision the server, generate and protect credentials, configure TLS and DNS, and maintain the client configuration without relying on a shared subscription repository. NiREvil/vless offers ready-made links and an established import path, but it places more trust in repository maintainers, hosted accounts, and third-party endpoints. A commercial provider subscription is another option because the provider operates the account and endpoint, although that does not transfer all operational responsibility to the customer. ## Maintenance, Upgrades, and GPL-3.0 Obligations The repository is not archived, and its last push was on 2026-10-15. That is recent source activity, but no GitHub releases are listed. The repository therefore has no documented stable release series, compatibility guarantee, formal migration guide, or release-specific changelog. Tracking `main` can expose readers to configuration and script changes that have not been described in release notes. Upgrade cost depends on which part is used. Subscribers may need to refresh URLs or verify imported entries. Panel users may need to rerun the external Wizard or review deployment settings. Rust users must account for manifest dependency changes and source updates, while contributors can use the `npm run format` and `npm run lint` scripts. The README does not document a production update schedule for the BPB panel or subscription files. The repository is licensed under GPL-3.0. Redistributing modified GPL-covered files or binaries can require corresponding source, license notices, and other GPL terms. This is not legal advice, and the GPL status of NiREvil/vless does not automatically determine the license of independent servers, hosted panels, or external links. Operators who publish modified components should inspect the repository `LICENSE` and the terms of each hosted service before redistribution. ## Conclusion Adopt NiREvil/vless if you already understand VLESS subscriptions, endpoint trust, and Cloudflare account requirements. Do not treat it as a managed VPN or assume that every listed endpoint is available. Inspect `sub/`, review `edge/assets/BPB-settings.dat` before uploading it, and check the GPL-3.0 terms before redistributing modified files or binaries. ## FAQ ### How do I install NiREvil/vless? The README does not provide installation commands for `RScanner`, `CFScanner`, or the subscription collection. It documents an external BPB Wizard workflow whose installer uses a Bash command that downloads `install.sh` from GitHub. ### Which clients can import NiREvil/vless subscription links? The README specifically names v2rayNG and Hiddify. It says to add a normal subscription link inside either client and then use URL Test. ### What are the RScanner and CFScanner binaries? `Cargo.toml` defines `RScanner` from `edge/proxies-main.rs` and `CFScanner` from `edge/cf-scanner.rs`. The README does not document their command-line arguments, scan criteria, output format, or operational limits. ## Sources - [Issues](https://github.com/NiREvil/vless/issues) - [License: GPL-3.0](https://github.com/NiREvil/vless/blob/main/LICENSE) - [NiREvil/vless on GitHub](https://github.com/NiREvil/vless) - [README](https://github.com/NiREvil/vless/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/nirevil-vless