Automic VaultAutomic Vault

brew

vacuum mit Homebrew, MacPorts, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install vacuum

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install vacuum

MacPorts ports tree · devel/vacuum/Portfile · Quelle: api.github.com

Windows

Scoopverifiziert · 92%
scoop install main/vacuum

Scoop official bucket manifest trees · bucket/vacuum.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

World's fastest OpenAPI & Swagger linter

Verlauf

Projektgeschichte und Nutzung

vacuum is a Go-based OpenAPI, AsyncAPI, and JSON Schema linter and API-quality toolkit. It was created as a fast, lightweight alternative in the same niche as Spectral while preserving compatibility with existing Spectral rulesets.

Projektgeschichte

The first GitHub release, v0.0.1, was published in May 2022 and described as an alpha but stable working release. The early changelog already included an OpenAPI rules engine, default rulesets, schema checks, a report command, Spectral report generation, and Docker packaging.

The project's README later positioned vacuum as the world's fastest OpenAPI, AsyncAPI, and JSON Schema linter, docs generator, and toolkit. Its development expanded beyond OpenAPI linting into HTML reports, a dashboard, documentation generation, overlays, OpenAPI collections, JSON Schema linting, and AsyncAPI support.

Adoptionsgeschichte

vacuum's adoption path is strongly package-manager oriented: the official README documents installation through a Homebrew tap, npm, yarn, curl installer, Docker images, GitHub Packages, and `go run`. The Homebrew formula, MacPorts, and Scoop entries in the input show it crossing into normal developer workstation package indexes.

The project targets CI and automated API governance workflows. The README includes a GitHub Actions installation pattern and notes token use to avoid GitHub API rate limits during automated installs.

Wie es verwendet wird

The common CLI path is `vacuum lint <your-openapi-spec.yaml>`, but the tool also exposes report, dashboard, HTML report, docs generation, bundle, language-server, overlay, schema, and ruleset-generation commands. The README emphasizes that it accepts YAML or JSON and supports OpenAPI 2, OpenAPI 3+, AsyncAPI 3, and JSON Schema documents.

Because vacuum is compatible with Spectral rulesets, package users can reuse existing API lint policies while benefiting from vacuum's Go binary distribution and speed-focused implementation.

Warum Paket-Nerds sich dafür interessieren

vacuum matters to package nerds because it is a single native CLI that replaces a chunk of Node-oriented API linting machinery for many workflows. That makes it attractive in Homebrew, Scoop, Docker, and CI setups where fast cold starts, simple binary distribution, and reproducible lint behavior matter.

Its rapid release cadence and widening command set make it a package-manager-visible example of the OpenAPI tooling ecosystem moving from JavaScript-only linters toward compiled CLIs that still interoperate with existing ruleset formats.

Zeitleiste

  • 2022: v0.0.1 initial GitHub release published with an alpha rules engine and reporting features.
  • 2022: README documents Homebrew tap, npm, yarn, curl, Docker, and Go execution paths.
  • 2026: v0.28 adds JSON Schema-specific linting.
  • 2026: v0.29 adds AsyncAPI 3 linting as a first-class document type.

Related projects

  • Spectral is the ruleset ecosystem vacuum explicitly supports.
  • OpenAPI, AsyncAPI, and JSON Schema are the specification families vacuum linting targets.
  • Docker, Homebrew, npm, yarn, and Go are official installation paths documented by the project.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für vacuum 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
./vacuum.conf.yaml~/.config/vacuum.conf.yaml./changes-rules.yaml~/.config/changes-rules.yaml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
vacuumcliglobales 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-26
Manager-Version0.30.0
Manager aktualisiert2026-07-26
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.30.0

https://github.com/daveshanley/vacuum

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:vacuum
Version0.30.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/vacuum
Homepagehttps://quobix.com/vacuum/
Repositoryhttps://github.com/daveshanley/vacuum
Upstream-Dokumentationhttps://quobix.com/vacuum
LizenzMIT
Quellarchivhttps://github.com/daveshanley/vacuum/archive/refs/tags/v0.30.0.tar.gz
Zuletzt aktualisiert2026-07-26T00:30:00+02:00
Pulseupdated
Build-Abhängigkeitengo, node
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 Namevacuum
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.

MacPorts95%

vacuum

sudo port install vacuum
  • normalized package name match
  • Abgeglichen nach: Vacuum
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/vacuum/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
Scoop95%

main/vacuum

scoop install main/vacuum
  • normalized package name match
  • Abgeglichen nach: Vacuum
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/vacuum.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