Quick guide
Which developer packages can macCurrent update on Mac?
macCurrent brings supported Python packages, standalone Go tools, global npm packages, Rust/Cargo tools and global Composer/PHP tools into the same Mac interface as your apps. Each installed copy keeps its environment, runtime or package-manager identity. Installation support depends on the source, compatibility and owning manager; project dependency support differs by ecosystem.
Which developer packages does macCurrent support?
| Package family | Supported update scope | Key limit |
|---|---|---|
| Python | Eligible environments, uv tools, pipx, Conda and supported Poetry, Pipenv and uv projects. | Project updates follow an existing lock file; scheduled automatic Python installation is disabled. |
| Go | Eligible standalone tools from the qualified golang.org/x/tools, golang.org/x/tools/gopls and golang.org/x/vuln families. | Does not upgrade the Go SDK or project go.mod / go.sum. |
| npm / Node.js | Eligible globally installed public npm packages across supported installations. | Project node_modules, package.json and lockfiles stay with project tools. |
| Rust / Cargo | Eligible installed command-line tools from the public crates.io registry. | Needs supported installation records, build settings and an installed compatible Rust compiler. |
| Composer / PHP | Eligible stable global Composer packages using a compatible installed PHP runtime. | Project dependencies and PHP runtime installation are outside this flow. |
| Homebrew | Supported installed formulae and casks through their matching Homebrew route. | Homebrew keeps control of its own installations. |
Start with the Python package guide, Go tool guide, or npm tool guide and editor extension guide. For the interpreter itself, see updating Python on Mac.
Rust and Cargo command-line tools
macCurrent reads supported Cargo installation records, checks eligible public crates.io releases and can update qualified command-line tools. It checks the installed Rust compiler, selected version and supported target and build settings before preparing an update.
Git, local and custom-registry sources need their owning Cargo workflow. Incomplete legacy installation records or unsupported custom configuration can also prevent an update. This route does not update your Rust toolchain or rewrite a project’s Cargo.toml and Cargo.lock. The Cargo installation reference explains how standalone binary installations differ from project dependencies.
Global Composer and PHP packages
Open Inventory > Packages > Composer / PHP after scanning. For an eligible stable global tool, choose Update Package or Update Selected. PHP and Composer must already be installed. macCurrent checks installed PHP choices, shows the exact package and destination, and runs a compatibility dry run before installation.
The update preserves existing dependency constraints. Shared dependencies may change while other directly required tools stay at their installed versions. Scripts and Composer plug-ins are disabled; installations that need those features or unsupported settings require Composer. If a command fails, review and repair the global installation through Composer before continuing.
Choosing PHP for a package update leaves your terminal default unchanged. Use a compatible PHP runtime when running the updated tool, too. The Composer global command reference explains the global installation context.
Global npm packages and Node.js compatibility
macCurrent checks global public npm packages and can update eligible installations. For an offered update, the Node/npm compatibility dialog shows installed runtime choices and checks the selected package’s requirements, including dependency requirements. Only a passing choice enables installation.
The package stays in its original global location. A remembered runtime choice is checked again before use, and your default Node/npm and terminal PATH stay unchanged. Updating the npm tool itself requires the verified tools belonging to that installation.
Review the installed copy before updating
- Scan your Mac, then open the matching package category.
- Select the installation you use and check its environment, destination and owning manager.
- Review the offered version, runtime requirements and update action. Resolve any compatibility or source problem before installing.
- Check the result. Use a package-specific recovery action when offered, or follow the owning manager’s repair instructions.
macCurrent runs on Apple silicon and Intel Macs with macOS 15 or later. The current release candidate is free. App replacement backups do not cover every package, plug-in or project; recovery depends on the update route. Read the source coverage page for apps, extensions and vendor updaters.
Frequently asked questions
Which developer packages can macCurrent update on Mac?
macCurrent supports eligible Python packages, qualified standalone Go tools, global public npm packages, Rust/Cargo command-line tools and stable global Composer packages. It also uses Homebrew for matching Homebrew installations. Each route has source, runtime and compatibility requirements.
Does macCurrent update all project dependencies?
Support differs by ecosystem. Supported Python project environments follow existing Poetry, Pipenv or uv lock files. npm, Go, Cargo and Composer project dependency files stay with their project tools.
Will selecting a runtime change my terminal default?
Choosing a compatible installed Node/npm or PHP runtime for a supported package update leaves your terminal default unchanged. Run the updated tool with a compatible runtime afterward as well.
Are packages included in Mac app backups?
App replacement backups do not cover every package, plug-in or project. Python and qualified Go or Cargo routes have their own recovery rules. Use the action and explanation for the selected item.