Automic VaultAutomic Vault

brew

meta-package-manager mit Homebrew, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install meta-package-manager

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install main/meta-package-manager

Scoop official bucket manifest trees · bucket/meta-package-manager.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Wrapper around all package managers with a unifying CLI

Befehle und Aliase

  • meta-package-manager
  • mpm

Verlauf

Projektgeschichte und Nutzung

Meta Package Manager, commonly invoked as mpm, is a unifying command-line wrapper around many native package managers. The project is maintained by kdeldycke and describes itself as a package-manager analogue to yt-dlp: one CLI that discovers package managers on the machine and normalizes common operations such as listing installed packages, searching, installing, removing, syncing metadata, upgrading, and exporting package inventories.

Projektgeschichte

The tool's history is tied less to one platform than to the long-standing problem of machines accumulating several package ecosystems at once. Its documentation and README show support across macOS, Linux, Windows, BSD-like systems, and managers including apt, brew, cargo, dnf, flatpak, gem, npm, pacman, pip, pipx, scoop, snap, winget, yarn, zypper, and others, with support varying by operation. Release notes and documentation also emphasize backup and restore manifests, release-age cooldowns as a supply-chain mitigation, and cross-platform standalone binaries.

Adoptionsgeschichte

In practice, mpm is a power-user and fleet-maintenance tool: it is useful when a workstation has Homebrew, pipx, npm, cargo, and OS packages side by side and the user wants one inventory or upgrade command. It sits near tools such as PackageKit, Ansible package modules, or platform-specific wrappers, but its niche is an interactive and scriptable local CLI rather than a configuration-management system.

Wie es verwendet wird

Homebrew and Scoop packaging reflect that niche: users install mpm through one package manager so it can inspect and orchestrate many others.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:package manager

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 4 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 1 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.

macOS
pyproject.toml~/Library/Application Support/mpm/config.toml
Unix
pyproject.toml~/.config/mpm/config.toml
Windows
pyproject.toml%APPDATA%\mpm\config.toml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
meta-package-managercliglobales Executable
mpmcliglobales 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-Version7.0.1
Manager aktualisiert2026-06-28
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://kdeldycke.github.io/meta-package-manager/

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:meta-package-manager
Version7.0.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/meta-package-manager
Homepagehttps://kdeldycke.github.io/meta-package-manager/
Repositoryhttps://github.com/kdeldycke/meta-package-manager
Upstream-Dokumentationhttps://github.com/kdeldycke/meta-package-manager#readme
LizenzGPL-2.0-or-later
Quellarchivhttps://files.pythonhosted.org/packages/88/8c/3a64fc201514510d906e7a9a37fc8f2d935f62aa939e2f9caa324d820e4a/meta_package_manager-7.0.1.tar.gz
Zuletzt aktualisiert2026-06-28T12:46:41Z
Pulseupdated
Abhängigkeitencertifi, libyaml, python@3.14, rpds-py
Build-Abhängigkeitenrust
Von macOS bereitgestellte Bibliothekenlibxml2, libxslt
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 Namemeta-package-manager
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Scoop95%

main/meta-package-manager

scoop install main/meta-package-manager
  • normalized package name match
  • Abgeglichen nach: Meta Package Manager
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/meta-package-manager.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

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