Automic VaultAutomic Vault

brew

mago mit Homebrew, Nix, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für mago in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install mago

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#mago

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

Windows

Windows Package Managerverifiziert · 92%
winget install --id CarthageSoftware.Mago -e

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

Überblick

Paketzusammenfassung

Toolchain for PHP to help developers write better code

Befehle und Aliase

  • mago

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für mago wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 2 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

BefehlArtSichtbarkeitHinweis
magocliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version1.43.0
Manager aktualisiert2026-07-05
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:mago
Version1.43.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/mago
Homepagehttps://github.com/carthage-software/mago
Repositoryhttps://github.com/carthage-software/mago
Upstream-Dokumentationhttps://mago.carthage.software/
LizenzApache-2.0 OR MIT
Quellarchivhttps://github.com/carthage-software/mago/releases/download/1.43.0/source-code.tar.gz
Zuletzt aktualisiert2026-07-05T16:20:06Z
Pulseupdated
Build-Abhängigkeitenpkgconf, rust
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namemago
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

mago

nix profile install nixpkgs#mago
  • normalized package name match
  • Abgeglichen nach: 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
  • Abgeglichen nach: 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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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