GlazePKG: one pacman-style command for every package manager on the machine

One syntax over the managers you already juggle

The pitch is stated in the README's own terms: one command for every package manager you have, with gpk described as yay for the whole machine, and the tool covers 46 package managers plus the applications you installed by hand, with zero config, one binary, on macOS, Linux and Windows. The problem it attacks is real and mundane. You already juggle brew, pip, cargo, npm, apt, pacman and the AUR, each with its own flags, its own search and its own answer to what is even installed, and moving to a new machine means relearning all of it. GlazePKG keeps the pacman and yay muscle memory and points it at everything else, with the short flags -S, -Ss, -Si, -Syu and -R alongside plain words. The description of the repository is narrower still, seeing all your installed packages in one place, and it names itself the official package manager for RyokuArch, which suggests the tool is aimed at users of that distribution as much as at anyone else.

Search runs across every manager in parallel

The command surface is short and readable:

gpk firefox               # search and pick something to install (like yay)
gpk -S ffmpeg             # install
gpk -S ffmpeg --aur       # install, scoped to one manager
gpk install [email protected]  # install a specific version (or --pick-version to choose)
gpk versions black        # list installable versions, newest first
gpk -Ss ripgrep           # search every manager at once
gpk -Syu                  # update everything
gpk -R foo                # remove  (-Rns to take orphaned deps too)
gpk downgrade foo         # roll back to an earlier version

The search behaviour is the part that matters most. If you are not sure which manager has a package, gpk searches them all and shows you the name, the version and the description, and if you mistype it, it suggests the fix. The version handling goes further than most wrappers: you can pin a package at a specific version, pick interactively from the available ones, roll back with downgrade, and compare versions across formats. A package you install by hand, outside any manager, is also visible to the tool, which closes the gap that makes a single view of a machine hard.

AUR without a helper, and what that means for reversibility

The AUR path is called out separately in the feature table, as AUR without a helper: gpk searches the AUR and builds with makepkg, and it shows you the PKGBUILD first. That last part is the significant detail. An AUR package is a build recipe fetched from the network and compiled on your machine, so a wrapper that hides the recipe would be hiding the part of the process a careful user wants to read. The README's framing is that gpk stands in for yay, and yay is a helper that automates the AUR, so the point of gpk here is to offer the same convenience without a second tool in the chain. The consequence to weigh is that an AUR build is not a binary you can remove with a single command the way a package from a repository is, so rollback and autoremove semantics differ from the rest of the tool.

Install paths, and who owns the file afterwards

There are five documented ways to get the tool. Homebrew on macOS and Linux:

brew install gpk

The AUR on Arch Linux:

yay -S gpk-bin

Nix on any Linux or macOS, either trying it without installing or installing it into a profile:

nix run github:neur0map/glazepkg          # try it without installing
nix profile install github:neur0map/glazepkg

A Go toolchain:

go install github.com/neur0map/glazepkg/cmd/gpk@latest

Or a pre-built binary from the releases page for macOS on ARM or Intel, Linux on x64 or ARM, or Windows on x64 or ARM. The upgrade story then depends on who put the file there, and the README has a table for it: gpk update replaces the binary in place and is meant for the pre-built downloads, while a package manager owns the file, so gpk points you at that manager instead of fighting it. The table maps Homebrew to brew upgrade gpk, the AUR to yay -S gpk-bin, Nix to nix profile upgrade gpk, Scoop and Chocolatey to their own update commands, and a release download or go install to gpk update.

Windows warns because the binary is unsigned

The README devotes a section to the Windows experience, and the message is that the warning is a false alarm. The Windows build is not signed yet, and antivirus tools often flag fresh unsigned programs made with Go, while the same code on macOS and Linux is fine. There are three ways to deal with it. You can skip the download and install with Go instead:

go install github.com/neur0map/glazepkg/cmd/gpk@latest

Or you can confirm the file is genuine, because every release ships a checksums.txt, and on PowerShell that means:

  Get-FileHash .\gpk-windows-amd64.exe -Algorithm SHA256

and comparing the result with the line for that file in checksums.txt. Or, once you have checked the file, you can unblock it with the Properties dialog and Unblock-File, and if the Windows protected your PC box appears, choose More info and Run anyway. The honest caveat the README gives is about work machines, where a missing Run anyway button means your IT department is blocking unsigned applications and nothing on the project side can change that.

The bare command opens a TUI, and the flags cover the scripting case

Running gpk with no arguments launches the terminal dashboard, which the README describes as searchable, snapshotable and diffable. Navigation is j and k, Tab switches managers, slash searches, s takes a snapshot, d diffs and e exports, and question mark shows the keybind reference. The dashboard is built with Bubble Tea, and the dependency list shows the rest of the Charm stack around it, bubbles for the components, lipgloss for styling, termenv for terminal detection and sahilm/fuzzy for the fuzzy matching that makes the search feel responsive. The other half of the tool is the typed command line, and the README is explicit that gpk is not only the dashboard, since every action has a typed command and the pacman and yay short flags work too, so you can drive it from a shell without opening the interface. The scriptability story rests on --json everywhere plus stable exit codes, and the intent stated in the feature table is to drop it behind a GUI or a CI job.

Hold, undo, export and the state of the project

The remaining features are about keeping control of the machine rather than about installing. You can hold a package so upgrades skip it, read the history and undo the last thing gpk did, autoremove orphans and clean the caches, export your whole setup to JSON and import it on the next machine, and run the whole thing from a snapshot. Two things in the documentation are worth a second look before you rely on them. The first is the manager count, which the README states as 46 in the headline and in the feature table but as 43 in the sentence describing the short flags, so treat the exact number as unsettled. The second is caching, described as scanning once and caching for ten days, which is fast to open and also means a package list can be up to ten days stale. The project is GPL-3.0 licensed, built with Go 1.25.0, and the repository carries COMPATIBILITY.md, a ROADMAP.md, a CHANGELOG.md, an example-theme.toml and a nix directory, with v0.6.10 published on 2026-09-22 and the last push on the same day.

Editorial conclusion

GlazePKG fits a developer moving between machines who keeps a dozen package managers and wants one search, one install command and one view of what is installed, with JSON output for scripting the whole thing into CI or a GUI. It does not fit someone who wants a single package manager, since the point of the tool is to sit on top of all of them, and it does not replace the managers themselves. Before adopting it, run gpk managers to see which backends are detected on your machine, check COMPATIBILITY.md for the ones you rely on, and read the AUR path carefully, because the AUR build with makepkg is the least reversible part of the workflow.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. neur0map/glazepkg on GitHub
4. README
5. Releases