macOS
brew install xraylocal Homebrew formula metadata
sudo port install xrayMacPorts ports tree · net/xray/Portfile · source: api.github.com
brew
Platform for building proxies to bypass network restrictions. Version 26.3.27 via Homebrew; verified from local package data.
install
brew install xraylocal Homebrew formula metadata
sudo port install xrayMacPorts ports tree · net/xray/Portfile · source: api.github.com
sudo apk add xrayAlpine Linux edge package indexes · xray · source: dl-cdn.alpinelinux.org
nix profile install nixpkgs#xraynixpkgs package indexes · pkgs/by-name/xr/xray/package.nix · source: api.github.com
scoop install main/xrayScoop official bucket manifest trees · bucket/xray.json · source: api.github.com
winget install --id XTLS.Xray-core -eWindows Package Manager source index · XTLS.Xray-core · source: cdn.winget.microsoft.com
overview
Platform for building proxies to bypass network restrictions
history
Xray-core is the Go networking core of Project X, a proxy and anti-censorship toolkit descended from v2ray-core and centered on XTLS, VLESS, REALITY, routing, DNS, and composable transports.
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.
security posture
broad file, network, media, or database tool signal. formula declares a Homebrew service.
orange risk · medium confidence · infrastructure
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
xray | cli | global executable |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
https://github.com/XTLS/Xray-core
install metadata
| Package key | brew:xray |
|---|---|
| Version | 26.3.27 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/xray |
| Homepage | https://xtls.github.io/ |
| Repository | https://github.com/XTLS/Xray-core |
| Upstream docs | https://xtls.github.io/en |
| License | MPL-2.0 AND CC-BY-SA-4.0 |
| Source archive | https://github.com/XTLS/Xray-core/archive/refs/tags/v26.3.27.tar.gz |
| Build dependencies | go |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | declared |
| Caveats | An example config is installed to $HOMEBREW_PREFIX/etc/xray/config.json |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | xray |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
xray
nix profile install nixpkgs#xrayxray 26.3.27-r0
Platform for building proxies to bypass network restrictions
https://github.com/XTLS/Xray-core
sudo apk add xrayxray
sudo port install xraymain/xray
scoop install main/xrayXTLS.Xray-core
winget install --id XTLS.Xray-core -esource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.