Automic VaultAutomic Vault

brew

mcap mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install mcap

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Serialization-agnostic container file format for pub/sub messages

Verlauf

Projektgeschichte und Nutzung

MCAP is an open file format and command-line tool for recording, inspecting, and converting publish/subscribe message logs. It is serialization-agnostic, which lets robotics and telemetry systems store ROS, Protobuf, JSON, and other message encodings in one container format.

Projektgeschichte

Foxglove's official documentation presents MCAP as a container format for pub/sub messages with a formal specification, language libraries, and a CLI. The GitHub release history shows the mcap-cli release stream beginning publicly in 2022, alongside the broader effort to make robotics logs easier to inspect outside one vendor or middleware stack.

By 2026 the CLI had advanced to a v0.2.x release line, and the official release notes identify the CLI as rewritten in Rust. That kind of implementation change matters for package managers because it affects build dependencies, binary distribution, and performance expectations.

Adoptionsgeschichte

MCAP adoption is strongest in robotics and observability workflows around Foxglove and ROS. The official documentation includes guides for getting started, the formal spec, and ecosystem integrations, while Homebrew packages the mcap executable as a convenient desktop and CI tool.

Unlike many robotics formats, MCAP was designed to be serialization-agnostic from the start. That made it attractive for package ecosystems because one CLI can inspect, validate, convert, and filter logs produced by different message schemas.

Wie es verwendet wird

Users install the mcap CLI to inspect metadata, validate files, recover or convert logs, and pipe message data into other tooling. Developers use the spec and language libraries when they need to produce or consume MCAP files directly from robots, simulations, or data pipelines.

The format is especially useful when logs must be archived, replayed, or shared between teams without assuming a single serializer or runtime.

Warum Paket-Nerds sich dafür interessieren

MCAP is package-nerd significant because it turns a robotics logging format into a normal command-line artifact. Having a Homebrew formula for mcap lets developers inspect large log files on laptops without installing an entire robotics distribution.

It also represents a newer class of packages where the file format, spec site, libraries, and CLI are all part of one developer-facing artifact.

Zeitleiste

  • 2022: Public mcap-cli GitHub releases began.
  • 2022: The CLI release stream iterated rapidly through early v0.0.x versions.
  • 2026: mcap-cli v0.1.0 and v0.2.0 releases were published, with v0.1.0 described as a Rust rewrite.
  • 2026: Homebrew packages the mcap command for local log inspection and conversion workflows.

Related projects

  • Related projects include Foxglove, ROS bags, rosbag2, Protobuf, FlatBuffers, JSON Schema, and robotics telemetry tools that need durable log containers.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:container

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • 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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
mcapcliglobales 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-25
Manager-Version0.3.0
Manager aktualisiert2026-07-15
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionreleases/mcap-cli/v0.3.0

https://github.com/foxglove/mcap

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:mcap
Version0.3.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/mcap
Homepagehttps://mcap.dev
Repositoryhttps://github.com/foxglove/mcap
Upstream-Dokumentationhttps://mcap.dev/
LizenzMIT
Quellarchivhttps://github.com/foxglove/mcap/archive/refs/tags/releases/mcap-cli/v0.3.0.tar.gz
Zuletzt aktualisiert2026-07-15T09:44:52Z
Pulseupdated
Build-Abhängigkeitenrust
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 Namemcap
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

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 package history
  • package relationship graph
  • package version freshness
  • package-page enrichment