install

Additional install commands

macOS

Homebrewverified · 100%

brew install mago

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#mago

nixpkgs package indexes · pkgs/by-name/ma/mago/package.nix · source: api.github.com

Windows

Windows Package Managerverified · 92%

winget install --id CarthageSoftware.Mago -e

Windows Package Manager source index · CarthageSoftware.Mago · source: cdn.winget.microsoft.com

overview

Package summary

Toolchain for PHP to help developers write better code

Project links

Commands and aliases

mago

history

Project history and usage

Mago is a Rust-written PHP toolchain that combines static analysis, linting, formatting, and guard-style checks in one binary. It targets PHP projects that want faster local and CI feedback without installing a PHP runtime for the tool itself.

Project history

The public GitHub repository was created in October 2024. The documentation brands Mago as an oxidized PHP toolchain and describes three core tools in one binary: analyzer, linter, and formatter.

By 2025 the project had a long beta release train toward 1.0, and by mid-2026 the documentation showed a latest 1.42.0 version. The docs also show configuration discovery, schema publishing for editors, project version pinning, self-update behavior, and WebAssembly playground support.

Adoption history

Mago's adoption is still young, but its packaging story is already broad for a PHP developer tool. Official docs list installation through the Carthage shell installer, Composer, Homebrew, Cargo, and Docker, while the supplied Homebrew input also lists Nix and winget packages.

The project has several thousand GitHub stars and more than a hundred forks, which is notable for a relatively new PHP toolchain and reflects interest in Rust-based replacements or complements for PHPStan, Psalm, PHP-CS-Fixer, and formatters.

How it is used

The standard workflow is to install Mago, run `mago init` in a PHP project, and then run `mago analyze`, `mago lint`, or `mago fmt`. The official docs say initialization detects project layout and writes `mago.toml`.

Mago discovers configuration from the workspace, `$XDG_CONFIG_HOME`, `~/.config`, and the home directory, looking for `mago` and `mago.dist` files in TOML, YAML, YML, or JSON formats. It also publishes JSON schemas so editors and CI can validate configuration.

Why package nerds care

Mago is package-nerd significant because it compresses several familiar PHP QA tools into one Rust binary. That changes packaging ergonomics: package managers can offer static analysis, linting, formatting, shell completions, schemas, and update workflows as a single install.

Its version-pinning and schema model are especially relevant to maintainers because code-formatting and lint behavior must be reproducible across local machines, CI, and editor integrations.

Timeline

2024: Public GitHub repository created.
2025: 1.0.0 beta releases published.
2026: Documentation shows the 1.42.0 stable line.
2026: Benchmarks and playground are promoted in official docs.

Related projects

PHPStan, Psalm, Phan, PHP-CS-Fixer, and Pretty PHP are adjacent PHP analysis, linting, and formatting tools referenced or benchmarked against in Mago's documentation.
Composer, Homebrew, Cargo, Docker, Nix, and winget are relevant distribution channels for the toolchain.

Sources

https://github.com/carthage-software/mago
https://github.com/carthage-software/mago/releases
https://mago.carthage.software/latest/en/
https://mago.carthage.software/latest/en/guide/configuration/
source_facts.package-manager
source_facts.repo

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for mago. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Build metadata lists 2 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: mago.toml
Windows: mago.toml

executables

Installed executables

Command	Kind	Exposure	Note
`mago`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version1.43.0

manager updated2026-07-05

local dataok

upstreamnot checked

latest detectednot detected

https://github.com/carthage-software/mago

infoNo cached GitHub release or tag data was available.https://github.com/carthage-software/magonone confidence

install metadata

Package metadata

Package key	brew:mago
Version	1.43.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/mago
Homepage	https://github.com/carthage-software/mago
Repository	https://github.com/carthage-software/mago
Upstream docs	https://mago.carthage.software/
License	Apache-2.0 OR MIT
Source archive	https://github.com/carthage-software/mago/releases/download/1.43.0/source-code.tar.gz
Last updated	2026-07-05T16:20:06Z
Pulse	updated
Build dependencies	pkgconf, rust
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	mago
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

mago

nix profile install nixpkgs#mago

normalized package name match
Matched by: Mago

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ma/mago/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

winget95%

CarthageSoftware.Mago

winget install --id CarthageSoftware.Mago -e

normalized package name match
Matched by: Mago

Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: CarthageSoftware.Mago from https://cdn.winget.microsoft.com/cache/source.msix

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/mago.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install mago with Homebrew, Nix, winget