gixy mit Homebrew, Nix installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• gixy

Projektgeschichte

Gixy began in the Yandex GitHub organization, where the official README described the goal as preventing security misconfiguration and automating flaw detection for NGINX. The original public repository dates to 2017 and documented a Python tool tested mainly on GNU/Linux.

A maintained GetPageSpeed-oriented fork under dvershinin/gixy extended the project after the original lineage slowed. That fork keeps the same basic analyzer shape while documenting Python 3.6 through 3.13 support, expanded checks, Homebrew installation, RPM packaging through GetPageSpeed, AUR packaging as gixy-ng, PyPI distribution as gixy-ng, and auto-fix options.

Adoptionsgeschichte

Gixy gained attention because NGINX configuration bugs are often security bugs hidden in ordinary deployment files. The original Yandex README presented a set of named plugins for SSRF, HTTP splitting, origin validation, header redefinition, host spoofing, referrer rules, multiline headers, and alias traversal.

The maintained fork broadened the checker catalog into injection, forgery, known CVE, TLS, path traversal, header security, access control, DNS, and config-performance categories. Package metadata in this batch shows Homebrew and Nix packaging, while the fork documents RPM, AUR, and PyPI channels.

Wie es verwendet wird

Practitioners run gixy against /etc/nginx/nginx.conf or another explicit NGINX configuration path. The tool prints findings with severity summaries and plugin names, making it useful during review of server blocks, reverse-proxy rules, and security headers.

The maintained documentation also supports skipping selected checks and previewing or applying fixes for many findings. That lets operators use Gixy as both a linter in CI and a local investigation tool before editing production web-server configuration.

Warum Paket-Nerds sich dafür interessieren

Gixy is notable to packagers because it packages NGINX security knowledge as a command-line static analyzer rather than a runtime module. It can be added to build, CI, or audit workflows without changing the running web server.

Its fork history is also instructive: the package ecosystem continued to need a Gixy-like tool after the original repository slowed, so a maintained fork carried the package name and expanded distribution.

Zeitleiste

• 2017: The Yandex gixy repository is created on GitHub and the v0.1.1 release is published.
• 2019: The dvershinin/gixy fork is created on GitHub.
• 2023: The maintained fork publishes v0.1.21 in its GitHub releases feed.
• 2026: The maintained fork documents Python 3.13 support, expanded checks, Homebrew installation, and gixy-ng distribution.

Related projects

• NGINX is the configuration language and deployment target analyzed by Gixy.
• The original yandex/gixy repository is the upstream lineage for the maintained dvershinin/gixy fork.
• PyPI, Homebrew, AUR, RPM repositories, and Nix are documented or packaged distribution paths.

Quellen

• https://api.github.com/repos/dvershinin/gixy
• https://api.github.com/repos/yandex/gixy
• https://github.com/dvershinin/gixy
• https://github.com/yandex/gixy
• https://gixy.getpagespeed.com/
• https://gixy.getpagespeed.com/configuration