# HyFetch: pride flag colors in the terminal and an active neofetch fork > HyFetch overlays LGBTQ+ pride flag colors on the neofetch terminal display and keeps the upstream dylanaraps/neofetch codebase alive, since that original repository stopped receiving updates. Its Rust core ships through PyPI with prebuilt binaries, but the Windows install path has a documented Python version discrepancy between the README and pyproject.toml. **hykilpikonna/hyfetch** — 🏳️‍🌈 🏳️‍⚧️ Neofetch with LGBTQ+ pride flags! - Repository: https://github.com/hykilpikonna/hyfetch - Stars: 2,120 · Forks: 167 - Language: Shell - License: MIT - Published: 2026-10-11 · Updated: 2026-10-11 · Language: en - Canonical page: https://hysenlabs.com/projects/hykilpikonna-hyfetch ## Two tools in one repository: pride flag overlay and an active neofetch replacement HyFetch does two distinct things and packages both into a single install. First, it overlays LGBTQ+ pride flag colors on the ASCII art logo that neofetch-style tools display in the terminal, replacing the default palette with colors drawn from the selected flag. Second, it keeps an updated version of the original neofetch script active, since the upstream repository at dylanaraps/neofetch stopped receiving updates. Users who want the updated neofetch behavior without any pride flag coloring can run it here under the command name neowofetch, chosen specifically to avoid conflicts with any existing neofetch installation on the system. Installing hyfetch delivers both the pride flag tool and the updated neofetch fork together, so each user gets both regardless of which they actually need. The repository root holds a standalone neofetch file alongside the Rust-based hyfetch codebase, and both are present after a standard install. ## Rust since 2.0.0, with a Python fallback for platforms without prebuilt binaries Version 2.0.0 moved the HyFetch core from Python to Rust, and the project distributes the Rust binaries through PyPI rather than requiring users to have a Rust toolchain installed. The hatchling build system reads the current version from Cargo.toml via a regex pattern, keeping the Python packaging and Rust build pipelines synchronized on every publish. The Rust workspace requires toolchain 1.75.0 as a minimum, as declared in Cargo.toml, and the Python floor for the PyPI distribution is 3.7, as stated in pyproject.toml. A PyPI user who skips the Cargo step entirely still gets the correct Rust binary for their platform. On platforms without a prebuilt binary, such as riscv64, the tool falls back automatically to the v1.99.0 Python implementation rather than refusing to install. That version runs older Python code rather than the current Rust build and is documented as a compatibility measure for unsupported architectures. The repository is MIT-licensed. ## Installing from PyPI and running the first configuration prompt PyPI is the documented recommended path. Two commands install hyfetch into the active Python environment: ```sh pip install wheel pip install -U hyfetch ``` For an isolated install that puts hyfetch in the path without affecting the active environment, pipx and uv are available: ```sh pipx install hyfetch ``` ```sh uv tool install hyfetch ``` On the first run, hyfetch opens an interactive prompt asking the user to choose a color system and a preset, with no extra flags required for that initial setup. Running hyfetch again afterward uses the saved configuration directly. To change settings after the initial setup, one flag opens the configuration menu: ```sh hyfetch -c ``` Configuration is stored in hyfetch.json, which also accepts manual edits for overrides such as the args key used in the MotD scenario described later. ## The lightness parameter controls how flag colors render against dark and light backgrounds Pride flag palettes can look wrong at brightness extremes, and the project provides a direct control for that. On a very dark terminal background, certain flags lose so much contrast that colors are hard to distinguish; on a light background, the same colors may look washed out. The configuration menu exposes a lightness parameter that must be set between 0 and 1. For the specific case of a dark terminal where the rainbow flag appears too dark, 0.7 is the starting value to try. Results vary by terminal background, so trying values from that point is the documented method. This setting controls only how flag colors are rendered, not which flag is selected. Applying a new value requires either returning to hyfetch -c or editing hyfetch.json directly, and the change takes effect on the next hyfetch invocation. Color system selection is a separate prompt during initial setup and governs which color encoding the terminal uses, independent of the lightness value. ## Windows setup requires Git 2.42.0 and a terminal with RGB color support Running HyFetch on Windows involves more setup than on Linux or macOS. Two explicit prerequisites apply before any install command: Python and Git, with Git at version 2.42.0 or newer. The Python version requirement appears differently in two places within the same repository, and the gap is worth checking before installing. The README's Windows section specifies "Install Python > 3.7", a strictly greater-than constraint that excludes Python 3.7 itself. The pyproject.toml file uses requires-python = ">=3.7", which is a greater-than-or-equal constraint that includes 3.7. Both files ship in the same repository and they disagree, so anyone running exactly Python 3.7 on Windows should verify which constraint the runtime enforces before depending on the tool. Terminal choice matters independently of the Python question. Windows cmd.exe cannot display RGB colors, and the README names Windows Terminal as a capable option. No graceful fallback is described for terminals that cannot handle the color format, so running hyfetch in cmd.exe will not produce the intended visual output. Install commands on Windows are otherwise the same pip, pipx, or uv invocations used on other platforms, run from Git Bash or a terminal that supports RGB colors. ## System packages cover a dozen distributions, but Cargo installation skips the bundled dependencies System packages are available for Arch Linux, Fedora, Nix, Guix, Slackware, Homebrew, openSUSE Tumbleweed, Gentoo, and Debian and Ubuntu, with Debian packages starting at Trixie and Ubuntu packages starting at Noble. A universal option also exists through Lure.sh. Users who prefer to build from source can install via Cargo: ```sh cargo install hyfetch ``` Cargo omits two things the PyPI package bundles: a fastfetch backend (when it is needed) and, on Windows, Git Bash as a prerequisite. Both require separate manual installation via the Cargo path, which is the stated reason PyPI is recommended over Cargo even for users who already have Rust. Two paths also exist for running neowofetch without a full hyfetch install. Via npm, no local installation is needed: ```sh npx neowofetch ``` A curl invocation runs it with no package manager at all: ```sh bash <(curl -sL nf.hydev.org) ``` ## MotD invocations lose the ASCII art unless stdout detection is explicitly turned off One documented failure case: running hyfetch or neowofetch inside a Message of the Day script produces no ASCII art and no colors. Stdout detection defaults to auto, and in a MotD context, that setting strips the visual elements before output reaches the terminal. Three workarounds are documented, and all three achieve the same result. First, add an args key to hyfetch.json with the value "--stdout=off", which applies the override globally to every hyfetch invocation. Second, pass --stdout=off directly on the neowofetch command line inside the MotD script, limiting the override to that specific call. Third, set the option in $HOME/.config/(neofetch|neowofetch)/config.conf to off, targeting the neowofetch config file only. No preference among the three is stated. The right choice depends on how broadly the override should apply: globally to all hyfetch runs, to one MotD invocation, or through the neowofetch configuration. MotD scripts frequently route output through a pipe rather than a direct terminal connection, and that piped path is exactly the context hyfetch's auto detection reacts to, which is why this scenario requires an explicit opt-out. ## Conclusion HyFetch suits users who want pride flag colors on a neofetch-style terminal readout, and it covers the gap left by the dylanaraps/neofetch codebase, which stopped receiving updates. Installing via PyPI bundles the most dependencies; Cargo requires fastfetch separately, plus Git Bash on Windows. On platforms without a prebuilt Rust binary, the fallback runs v1.99.0 in Python, not the current Rust build. Before deploying on Windows, compare the README's Python above 3.7 instruction against pyproject.toml's floor of 3.7, since those sources disagree. For MotD use, set args to --stdout=off in hyfetch.json before deploying. ## FAQ ### What is HyFetch? HyFetch is a terminal system information tool that displays machine specs alongside ASCII art colored with LGBTQ+ pride flag palettes. It also maintains the upstream dylanaraps/neofetch codebase, which stopped receiving updates from its original author. ### How do I install HyFetch? The recommended path is via PyPI using pip install -U hyfetch, or pipx install hyfetch and uv tool install hyfetch for isolated installs. System packages are available for Arch Linux, Fedora, Debian starting at Trixie, Ubuntu starting at Noble, and several other distributions. ### How do I change my HyFetch configuration? Run hyfetch -c to open the configuration menu. Settings are stored in hyfetch.json, which can also be edited directly for overrides such as the --stdout=off argument. ### Does HyFetch work on Windows? The README documents a Windows install path that requires Python and Git 2.42.0 or newer, plus a terminal with RGB color support such as Windows Terminal. The default cmd.exe cannot display the colors. ### What is neowofetch? neowofetch is the command name for the updated neofetch script included in this repository. It runs the system information display without the pride flag color overlay and is available via pip install hyfetch or as a standalone run through npx neowofetch. ## Sources - [hykilpikonna/hyfetch on GitHub](https://github.com/hykilpikonna/hyfetch) - [Issues](https://github.com/hykilpikonna/hyfetch/issues) - [License: MIT](https://github.com/hykilpikonna/hyfetch/blob/master/LICENSE) - [README](https://github.com/hykilpikonna/hyfetch/blob/master/README.md) - [Releases](https://github.com/hykilpikonna/hyfetch/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/hykilpikonna-hyfetch