vacuum
MIT
An extremely fast OpenAPI linter written in Go, Spectral-ruleset compatible, built to lint very large specifications and whole estates in the time a CI step can afford.
OpenAPIOpenAPI Overlay
Specifications it implements
What this tool does to each specification, in the role vocabulary. Follow a standard through to standards.apievangelist.com for what it actually specifies.
| Standard | Role | What that means |
|---|---|---|
| OpenAPI | validates |
|
| OpenAPI Overlay | validates |
Using this from an agent
- Interfaces
clilibrarycontainer- Install
-
go
github.com/daveshanley/vacuumnpm@quobix/vacuum - Invoke
vacuum lint <spec.yaml> --ruleset <ruleset.yaml> --details- Consumes
- openapi
- Emits
- json, sarif, junit, html, pretty
- Runtime
- Runs offline Deterministic Read-only No credentials
Where it applies
Jobs this tool actually does, and the surface each one is exercised on.
Lint hundreds or thousands of OpenAPI documents in one pass, where Spectral would be too slow.
ci-pipelinecoding-agent
Produce an HTML governance report for a human reviewer from a machine run.
ci-pipeline
Reuse an existing Spectral ruleset without rewriting it, on a faster runtime.
coding-agent
- Website
- https://quobix.com/vacuum
- Repository
- https://github.com/daveshanley/vacuum
- License
- MIT — reported by the GitHub API, verified 2026-09-17
- Stars
- 1124 · last commit 2026-09-15
- Matching caveat
- The name is an ordinary English word, so the job-corpus matcher cannot use it — sampled matches were "Sweep, mop, and vacuum floors", "repairing advanced vacuum systems" The bare name is blocked in the matcher, so this count reflects only qualified matches. Real adoption needs another source.
Reading this as an agent? Don't scrape the page — this entry is published as
structured data at
arrow_back
All tools by adoption
/tools.json,
against the tool.schema.json
schema, using the roles.json
vocabulary. Start at /llms.txt.