Automic VaultAutomic Vault

brew

使用 Homebrew, MacPorts, scoop 安装 vacuum

查看 vacuum 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install vacuum

local Homebrew formula metadata

MacPorts已验证 · 94%
sudo port install vacuum

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

Windows

Scoop已验证 · 92%
scoop install main/vacuum

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

概览

软件包摘要

World's fastest OpenAPI & Swagger linter

命令和别名

  • vacuum

历史

项目历史与用法

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.

项目历史

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.

采用历史

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.

使用方式

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.

为什么软件包爱好者会关心

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.

时间线

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

安全态势

尚未找到受保护工具覆盖

没有找到 vacuum 的匹配本地密钥处理 manifest。Nucleus 软件包元数据仍在此发布,以便未来覆盖拥有稳定的软件包 URL。

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 构建元数据列出 2 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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

可执行文件

已安装的可执行文件

命令类型暴露范围备注
vacuumcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-26
管理器版本0.30.0
管理器更新时间2026-07-26
本地数据OK
上游当前
检测到的最新版本v0.30.0

https://github.com/daveshanley/vacuum

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:vacuum
版本0.30.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/vacuum
主页https://quobix.com/vacuum/
仓库https://github.com/daveshanley/vacuum
上游文档https://quobix.com/vacuum
许可证MIT
源码归档https://github.com/daveshanley/vacuum/archive/refs/tags/v0.30.0.tar.gz
最后更新2026-07-26T00:30:00+02:00
Pulseupdated
构建依赖go, node
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

MacPorts95%

vacuum

sudo port install vacuum
  • normalized package name match
  • 匹配方式: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
  • 匹配方式: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

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • 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