Our take
Activeregular commits and releases- Activity
- 57
- Community
- 59
- Issues
- 21
- Pull requests
- 63
+4 stars in the last 7 days
pkgx is an actively maintained, Apache-2.0-licensed tool runner with broad contributor participation, though teams should account for platform and package coverage differences.
Good fit if
- You want to run developer tools or specific versions without installing them system-wide.
- Your workflow uses scripts, CI, or Docker and can benefit from declaring tools at the point of use.
- You are comfortable with a Rust-based project that has regular commits and releases and contributions from many people.
Look elsewhere if
- You need full Windows package coverage, which the project describes as limited and experimental.
- You need an install-to-system package manager as the main interface. The README points to the separate pkgm project for that.
- You need a project whose recent issue handling is clearly demonstrated by its metrics. No issues were recorded as closed in the measured 90-day period.
All health signals
| Last commit | 2026-08-26 (1 month ago) |
|---|---|
| Commits, last 90 days | 12 |
| Releases, last 12 months | 8 (latest v2.11.0, 2026-07-22) |
| Contributors | 62 (top contributor: 71% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 6 (typically merged in 0 days) |
| Project age | 4 years |
Checked on 2026-10-08 with the GitHub API.
Overview
pkgx is a command-line package runner for getting developer tools when you need them, without installing them system-wide. It can run a requested tool or version on demand, keeping downloads in ~/.pkgx and leaving the wider system untouched.
It is aimed at developers who need different toolchains across projects or want scripts and CI jobs to declare their tools directly. Its surrounding ecosystem includes dev for project environments and pkgm for installing packages to /usr/local.
Key Features
- Run tools on demand, for example
pkgx deno, without a global installation. - Request particular versions, such as
pkgx node@14orpkgx python@2. - Use
+packagesyntax in scripts to make tools available while a script runs. - Run package-manager tools from other language ecosystems, including
uvxandbunx. - Query which packages are available from the command line or browse the package listing at pkgx.dev.
- Use pkgx in CI workflows, Docker images, and supported macOS, Linux, and Windows environments.
Use Cases
- Developers working across projects with different language or tool versions can run the version each project needs without changing system-wide installs.
- Script authors can declare tools in a shebang, making dependencies available for a script run without asking users to install each tool globally.
- CI maintainers can fetch command-line tools on demand in a workflow rather than relying on preinstalled tools on the runner.
- Teams building Rust projects can use the separate
devtool to detect and provide project dependencies based on key files.
What you need
Detected in the repository
- Rust (from Cargo.toml)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install with Homebrew or the project’s installer:
brew install pkgx || curl https://pkgx.sh | sh
See the README and documentation for platform requirements and usage details.
Alternatives
- cargo-binstall: cargo-binstall installs prebuilt binaries for Rust crates, while pkgx runs versioned developer tools on demand across projects and environments.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| pkgx | Rust | Apache-2.0 | 9.9k | Active |
| cargo-binstall | Rust | GPL-3.0 | 2.9k | Active |
Considerations
- Windows support is experimental and has limited package availability. Linux requires glibc 2.28 or later and libgcc; check the README for platform details.
- The project is active, with regular commits and releases and contributions from dozens of contributors. Its measured issue-closure count was zero over the latest 90-day window, so issue responsiveness may be harder to assess from that period.
- The project is licensed under Apache-2.0. Review that license against your organization’s distribution and compliance requirements.
- The supplied project requirements identify Rust and CI, but do not identify tests. Confirm the testing and validation practices that matter to your team before adopting it.
Found this useful?
Share it with someone who would like pkgx.