pkg⋅mgr²
New package managers ·
Find and manage tools from five more package managers, including every installed pkgx version.
You install one CLI with pnpm, another with Bun, a Python app with pipx, and a Go command straight from its source package. Then you use pkgx to run a tool without adding it to your PATH. A month later, you have five places to check for updates.
We’ve added all five to Package Manager Manager. You can see their installed tools alongside your Homebrew, npm, uv, and Cargo packages, check for newer versions, and update or remove them from the same window. You can install tools locally too.
Your global pnpm and Bun packages now appear in the JavaScript section alongside npm and the npx cache. The inventory keeps the manager’s name with each package, so you can tell which installation you’re looking at if you’ve installed the same tool more than once.
Install uses pnpm add --global package@latest or bun add --global package@latest. Updates use the corresponding update --global --latest command; removals use remove --global. You keep your existing global directories and package-manager setup.
This covers global tools. PMM does not scan the dependencies in every project’s node_modules directory.
Python applications installed with pipx now appear in the Python section alongside uv tools and uvx environments. You can inspect their versions, environment locations, and executable names, then run pipx upgrade or pipx uninstall from the detail pane. New local installs use pipx install.
pipx keeps each app in its own environment. PMM uses that environment’s name for actions, including suffixed installs, while linking to the underlying package on PyPI. Removing one suffixed copy should not target a different install with the same package name.
A Go binary can tell you where it came from. PMM reads its embedded build metadata with go version -m to recover the command’s package path and module version. It looks in GOBIN, or the first GOPATH entry’s bin directory, usually ~/go/bin.
For a command such as golang.org/x/tools/cmd/goimports, PMM checks the module golang.org/x/tools for a newer version, then updates the command with go install golang.org/x/tools/cmd/goimports@latest. Install uses the same command. Package details link to pkg.go.dev and the source repository where PMM can identify it.
Go has no uninstall command. PMM checks that the file is in your Go binary directory and that its embedded package path still matches before removing it. If Go is unavailable or the file no longer matches, the app refuses the removal. PMM leaves unrelated binaries in the same directory untouched.
PMM reads your pkgx packages from PKGX_DIR, usually ~/.pkgx. You can inspect their installed versions and paths, and check for newer versions available for the host’s operating system and architecture.
As with mise tools and uv-managed Pythons, you can keep several versions installed at once. Updating a pkgx package installs the newer version alongside the older ones. Uninstall removes the displayed version; PMM keeps any remaining versions in the inventory and points subsequent actions at a surviving installation.
Local installs use pkgx +project true. Updates request the target version explicitly with pkgx +project@version true, because an unversioned request can reuse an older cached copy. Before removal, PMM checks the resolved path inside your pkgx directory and refuses symlinked package paths.
Remote Hosts includes these five managers in agentless Linux inventory, with update and uninstall actions over SSH. Remote Macs need a compatible PMM build in /Applications. Each host keeps its own Installed and Outdated lists.
New installs remain local-only. The corresponding manager must already be available, and update checks need access to its registry or module source. Missing version metadata does not hide an installed package.
sabrimete contributed all five integrations: pnpm, Bun, pipx, Go, and pkgx. We checked scoped JavaScript packages, suffixed pipx environments, Go module metadata, and pkgx updates that preserve older versions. All 382 tests passed before the pkgx merge, alongside an isolated check with the real pkgx binary.
Get the latest release and refresh your inventory. If your tools still don’t show up, open an issue. To add another manager, start with the contributor checklist.