xray を Homebrew, apk, MacPorts, Nix, scoop, winget でインストール

プロジェクトリンク

• ホームページ
• リポジトリ

コマンドとエイリアス

• xray

プロジェクトの歴史

The Xray-core README says Project X originates from the XTLS protocol and provides tools such as Xray-core and REALITY. It also explicitly credits Xray-core v1.0.0 as a fork of v2fly-core commit 9a03cc5, after which the project accumulated many independent enhancements.

The v1.0.0 release in November 2020 framed the fork as a new beginning. Its notes said Xray-core was heavily modified from v2ray-core, merged ctl functionality into one executable, kept similar configuration ideas, changed environment/API naming to XRAY, exposed raw protocol ReadV across platforms, and provided VLESS and Trojan XTLS support.

The official documentation now cautions that Xray-core has evolved independently for a long time and should not be treated as a fully compatible v2ray-core drop-in replacement. It highlights complete support for VLESS, XTLS Vision, REALITY, multiple XTLS flow-control modes, and performance work such as Splice in suitable scenarios.

採用の歴史

Xray's adoption is broad inside the censorship-circumvention and proxy-client ecosystem. The README lists official installation routes, Docker images, web panels, one-click installers, Magisk packages, Homebrew, many GUI clients across OpenWrt, Windows, Android, iOS, macOS, Linux, and HarmonyOS, plus wrappers and downstream cores.

Its ecosystem grew around protocols and deployment recipes rather than a single UI. The Xray-examples repository, REALITY examples, VLESS-XTLS-Vision examples, install scripts, and GUI clients show that users usually consume Xray-core as an engine under profiles, panels, routers, mobile apps, or server setup scripts.

使われ方

Practical usage is configuration-driven. Operators define inbound and outbound protocols, routing and DNS rules, transport settings, fallbacks, TLS or REALITY behavior, and platform-specific service wrappers; the xray executable then runs the core proxy service.

Common package-manager users install xray when they want the core binary on macOS, Linux, routers, servers, or CI-built images. More casual users often encounter it indirectly through clients such as v2rayN, v2rayNG, OpenWrt passwall packages, or web panels that generate configuration.

パッケージ好きにとっての重要性

Xray is significant because it is both a single package and a protocol ecosystem. The Homebrew formula points at one executable, but the surrounding package graph includes install scripts, Docker images, GUI wrappers, router packages, mobile clients, panels, example repositories, and protocol documentation.

It is also a modern example of infrastructure software whose history matters for compatibility. Knowing that Xray branched from v2ray-core but evolved independently explains why configs may look familiar while APIs, environment variables, protocols, and operational assumptions differ.

タイムライン

• 2020-11-25: Xray-core v1.0.0 was published as a fork-derived new beginning from v2fly-core.
• 2023-03-09: Xray-core v1.8.0 release notes introduced REALITY material and XTLS Vision security changes.
• 2025-2026: The project moved to date-like release numbering such as v25.x and v26.x in GitHub releases.
• 2026-06-27: GitHub lists Xray-core v26.6.27 among current releases.

Related projects

• v2ray-core and v2fly-core: the upstream lineage from which Xray-core branched.
• XTLS, VLESS, XTLS Vision, REALITY, XUDP, and XHTTP: protocol and transport work central to Project X.
• XTLS/Xray-examples and XTLS/REALITY: official example and protocol repositories used by operators.
• v2rayN, v2rayNG, PassWall, Marzban, Hiddify, and related clients or panels: common downstream ways people operate Xray-core.

ソース

• https://github.com/XTLS/Xray-core
• https://github.com/XTLS/Xray-core/releases
• https://github.com/XTLS/Xray-core/releases/tag/v1.0.0
• https://github.com/XTLS/Xray-core/releases/tag/v1.8.0
• https://github.com/XTLS/Xray-examples
• https://raw.githubusercontent.com/XTLS/Xray-core/main/README.md
• https://xtls.github.io/en/