OpenAPI contract linters for a small team's merge gate

Redocly CLI's spec-only ruleset is our choice for a first OpenAPI merge gate. Vacuum, oasdiff and Speakeasy offer native binaries with different strengths in rules, validation and multi-file linting.

PRACTICAL PICKSPreferredPickOur Preferred PickFirst structural merge gate$0

Redocly CLI

Its spec ruleset checks the contract against the OpenAPI specification only, every rule an error, with no configuration file. Free, MIT, no account, maintained by Redocly.

Needs Node.js 22.12 or Docker; pin the version, and set REDOCLY_TELEMETRY=off to stop usage data.

Why Redocly CLI is our Pick
Newcomer assessment

No Rising Star selected

AuditAPI does not establish the structural-only gate this reader needs. Speakeasy already sold API linting. OpenLint documents local linting, but a first release date for a distinct new product could not be established.

An unknown first release date rules out a newcomer award.

Who is this article for? Small API teams with an OpenAPI contract in their repository who want one command, run locally and in CI, that fails a pull request when the contract breaks the specification.

About 21 min read

What Preferred Pick, Rising Star and Ready to Rock mean

The quick list

Start with Redocly CLI for a first structural gate. All four are free. Compare what fails the run by default, what each needs installed, and who keeps it maintained.

All four are free, open-source command-line tools with no account, checked November 6, 2026. CI time, keeping the version pinned and deciding which warnings should block a merge are the real costs. Redocly and SmartBear sell separate hosted products that this comparison does not cover.

The comparison at a glance

Compare what each tool fails by default, what it needs installed, how it reports to CI, and how well it is maintained.

Order follows our verdict for a small team's first merge gate, not a speed or popularity ranking. Redocly CLI is first, followed by Vacuum, oasdiff and Speakeasy. Oasdiff and Speakeasy have equal totals; maintenance, security and supply chain decide their order. All four remain selectable.

OpenAPI contract linters for a local and CI merge gate
FeatureRedocly CLIVacuumoasdiffSpeakeasy OpenAPI CLI
Editorial score / 54.404.033.953.95
Best fitA first structural merge gate with a ready-made spec-only rulesetA Node-free single binary, or Spectral-style rules without SpectralOne installation for single-contract validation and compatibility checksNative multi-file linting with configurable governance rules
Price and license$0; MIT; no account$0; MIT; no account$0; Apache-2.0; no account$0; MIT; no account
Starting configurationNone: --extends=spec on the command lineNone: recommended rules run by defaultRun oasdiff validate openapi.yamlRun openapi spec lint openapi.yaml; default all ruleset
Install and runtimenpm or npx with Node.js 22.12+ (Node.js 20 deprecated); Docker imageNative binary via Homebrew, install script, Docker or Go; npm wrapper needs Node.js 24.16+Native Windows, macOS and Linux binaries; Go, Homebrew or DockerNative Windows, macOS and Linux binary; Homebrew, script or Go
Latest release2.65.0, October 19, 2026; several a week, minor versions can add rules0.33.2, October 19, 2026; pre-1.0, several a month1.35.0, October 28, 2026; validation completeness and ordering fixes1.26.3, November 2, 2026; lint-fix and referenced-document improvements
Security and supply chain2026 advisories in split and respect, fixed June 2026; no runtime dependencies since 2.34.0No published advisoriesPublished external-reference and git-input advisories; use a current versionNo advisories published on its security page; no security policy
Reader reviewsNo reviews yet. Write a reviewNo reviews yet. Write a reviewNo reviews yet.No reviews yet.

Public-source research checked October 19, 2026. All four are free to run locally, checked November 6, 2026. CI time and agreeing which warnings block a merge are the real costs. Pin the version of whichever tool you choose. In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Redocly CLI 2.57.0, Vacuum 0.30.6 and Spectral CLI 6.16.3 each named a missing path parameter in one small fictional contract and failed it (earlier check record). That check did not decide our Pick. Breaking-change detection between versions is a separate job.

All features and sources 15 criteria

Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.

Running the merge gate

Show 8 criteria
Running the merge gate
FeatureRedocly CLIVacuumoasdiffSpeakeasy OpenAPI CLI
Starting configurationNone: --extends=spec on the command lineNone: recommended rules run by defaultRun oasdiff validate openapi.yamlRun openapi spec lint openapi.yaml; default all ruleset
Specification-only rulesspec ruleset: follows the specification, every rule an errorNo separate set; recommended errors include a missing operation ID and API descriptionPer-RFC validation command, separate from breaking-change checksNo dedicated spec-only set documented; tune security and style rules
Exit status in CINon-zero on failure (CI guide); exact codes not listed in the lint reference0 clean, 1 at or above --fail-severity (default error), 2 tool error or rule timeoutValidation findings documented; exact validation exit codes need confirmationREADME does not enumerate codes; CI use documented by the maker
OpenAPI 3.2Supported; 3.2 fixes in the October 2026 changelogParsed through libopenapi, which supports 3.0 to 3.2Single-contract validation documented; exact 3.2 coverage not establishedMaker documents 3.2 support
Install and runtimenpm or npx with Node.js 22.12+ (Node.js 20 deprecated); Docker imageNative binary via Homebrew, install script, Docker or Go; npm wrapper needs Node.js 24.16+Native Windows, macOS and Linux binaries; Go, Homebrew or DockerNative Windows, macOS and Linux binary; Homebrew, script or Go
CI outputGitHub Actions annotations, JSON, JUnit, Checkstyle, Code Climate, MarkdownPipeline summary; JSON, Spectral-format and HTML reports; official Action (fails below score 70 by default)Available CI output formats not confirmedJSON with external source files and coordinates; human-readable output
Growing the rulesConfigurable rules in redocly.yaml; JavaScript plugins; own formatSpectral-style YAML and JSON rulesets within documented limits; JavaScript functions; OWASP setPer-RFC checks; less custom governance controlSemantic, style, security and schema rules; custom TypeScript without Node.js
Accepting existing problems--generate-ignore-file writes a lint-ignore file--ignore-file with result paths or JSONPathNot established for validatePer-rule disabling and configuration; baseline not established
Sources for running the merge gate

Redocly lint reference, spec ruleset and CI guide; Vacuum README, exit codes, GitHub Action and rule source; Spectral CLI guide and README. Incumbent capabilities checked October 19, 2026. Oasdiff and Speakeasy repositories and documentation checked November 6, 2026.

Upkeep, security and data

Show 7 criteria
Upkeep, security and data
FeatureRedocly CLIVacuumoasdiffSpeakeasy OpenAPI CLI
Editorial score / 54.404.033.953.95
Latest release2.65.0, October 19, 2026; several a week, minor versions can add rules0.33.2, October 19, 2026; pre-1.0, several a month1.35.0, October 28, 2026; validation completeness and ordering fixes1.26.3, November 2, 2026; lint-fix and referenced-document improvements
MaintainersRedocly (company)One main maintainer (Dave Shanley)Public repository led by Reuven HarrisonSpeakeasy; public contributors and source
Security and supply chain2026 advisories in split and respect, fixed June 2026; no runtime dependencies since 2.34.0No published advisoriesPublished external-reference and git-input advisories; use a current versionNo advisories published on its security page; no security policy
Sent by defaultAnonymous usage data on each run; REDOCLY_TELEMETRY=offRelease check at most every 12 hours; --no-update-checkLocal command; background data collection not establishedLocal command; background data collection not established
Open issue to plan forRule additions in minor releases; pin the versionSome rules can fire twice non-deterministically (#938)Open requests cover allOf conflicts and readOnly/writeOnly validationDefault rules can reject a valid public API for missing authentication
AI features (not scored)Experimental generate-spec --with-ai; Claude Code is the default providerNone documented for lintingNot needed for local validationNot needed for local linting
Sources for upkeep, security and data

Redocly changelog, usage data and advisory; Vacuum releases and issue #938; Spectral releases, SmartBear update, OSV record and issue #2729; npm registry records. Incumbent findings checked October 19, 2026; oasdiff releases, security, Speakeasy releases and security checked November 6, 2026. AI features carry no weight in our judgment.

What matters when choosing

Redocly CLI is our Preferred Pick for a small team adding its first OpenAPI check before merge. Run it with its spec ruleset: redocly lint openapi.yaml --extends=spec. That ruleset is documented to follow the OpenAPI specification “as closely as possible”, and every rule in it is an error, so a missing path parameter, an unresolved $ref or a duplicate operation ID fails the run without style opinions mixed in. It needs no configuration file, is free under the MIT license and needs no account. Redocly, the company, releases it several times a week; version 2.65.0 came out on October 19, 2026. Since version 2.34.0 in June 2026 the npm package has no runtime dependencies, which narrows what a fresh install can pull in. Spec ruleset, lint options, changelog, repository and license

In our fixed-weight scoring Redocly CLI finished 0.375 ahead of Vacuum on our five-point scale. Its advantage rests on its spec-only ruleset and documented maintenance and supply-chain practices. Its compromises: it needs Node.js 22.12 or later (Node.js 20 is deprecated) or its Docker image, and it sends anonymous usage data on every run unless you set REDOCLY_TELEMETRY=off. Releases are frequent and minor versions can add rules, even to the spec ruleset, so pin the version in your project and upgrade deliberately. Its default recommended ruleset is opinionated: it also asks for servers, a license and a security declaration, which is policy rather than proof that a contract is broken. Usage data, rulesets, recommended ruleset

Also consider Vacuum if you want a single native binary without Node.js, or Spectral-format rules. It installs through Homebrew, a shell script, Docker or Go, documents its exit codes plainly (0 clean, 1 findings at or above your threshold, 2 a tool error or a rule timeout) and runs Spectral-style YAML and JSON rulesets within documented limits. It is maintained mainly by one developer and is still before version 1.0, with several releases a month. Its default recommended rules also treat a missing operation ID or API description as errors, so expect to tune them for a first gate. Vacuum, exit codes

Oasdiff and Speakeasy are worth comparing when you want a native binary. Oasdiff’s validate command checks one contract for specification violations, alongside its better-known breaking-change commands. Speakeasy’s openapi spec lint offers configurable rules and multi-file linting, but its default all ruleset mixes structure, style and security policy. Neither displaces Redocly’s ready-made specification-only starting point. oasdiff repository, Speakeasy repository (checked November 6, 2026).

No Rising Star selected. AuditAPI’s grade-based gate does not establish the structural-only failure behavior this reader needs. Speakeasy already sold API linting before releasing this tool. OpenLint documents installation and linting, but we could not establish a first release date for a distinct new product. It remains an alternative, without a newcomer award. AuditAPI, Speakeasy launch, OpenLint (checked November 6, 2026).

All four compared commands are free to run locally without an account. CI time and agreeing which warnings should block a merge remain real costs. These tools check one version of a contract; detecting changes that break existing clients needs a comparison of the old and new versions. In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Redocly CLI, Vacuum and Spectral each named a missing path parameter in a small broken contract and failed it. That check did not decide this Pick. Earlier check record, October 1, 2026

Disclosure: Practical Picks articles are researched and written with AI, currently Anthropic’s Claude. Redocly CLI’s experimental generate-spec command can use Claude Code, its default AI provider, to draft an OpenAPI description. We have no relationship with Redocly or Anthropic over this article, and this Claude link carried no weight in our judgment. generate-spec

Redocly CLI

Preferred Pick · first structural merge gate

$0MIT · no account

Run its spec ruleset for a first merge gate: every rule follows the OpenAPI specification and fails the run, with no configuration file. Pin the version and set REDOCLY_TELEMETRY=off if you do not want usage data sent.

Reasons to choose it

  • Documented spec-only ruleset; every rule is an error
  • Maintained by Redocly with releases several times a week
  • No runtime dependencies in the npm package since 2.34.0

What to watch

  • Needs Node.js 22.12 or later, or Docker
  • Sends anonymous usage data on each run unless turned off
  • Minor releases can add rules, even to the spec ruleset

Redocly CLI ships four rulesets. spec follows the specification and makes every rule an error; minimal suits an existing API that has never been linted; recommended, the default, is what Redocly calls its “unabashedly opinionated” view of a good API; and recommended-strict turns its warnings into errors. With no configuration file, redocly lint openapi.yaml --extends=spec gives a structural gate. The spec ruleset includes path-parameters-defined, no-unresolved-refs, operation-operationId-unique, no-identical-paths and struct, which checks the document’s shape. Redocly’s CI guide says a failed command returns a value greater than zero, so the job fails when an error-level rule fires. Rulesets, spec ruleset, lint and bundle in CI

When the team is ready for more, add a redocly.yaml that extends a ruleset and changes individual rule severities, write configurable rules without code, or add JavaScript plugins. --generate-ignore-file records today’s problems in a .redocly.lint-ignore.yaml file so that only new problems fail. Output formats include github-actions annotations, json, junit, checkstyle, codeclimate and markdown. Its changelog includes OpenAPI 3.2 fixes as recently as October 2026. It does not use Spectral’s ruleset format; Redocly publishes a guide for moving from Spectral. Lint options, migrate from Spectral, changelog

Read the full Redocly CLI analysis and sources

Keep upgrades deliberate

Redocly published more than 120 releases of version 2 between January 1 and October 19, 2026. That is a sign of active maintenance, but it also means behavior changes often: version 2.46.0 (August 7, 2026) added the spec-ref-siblings rule to the spec ruleset, and 2.57.0 (September 30, 2026) warned that a stricter no-enum-type-mismatch check “may include new errors”. Pin the version in package.json or call npx @redocly/cli@<version>, and upgrade in its own pull request. Version 2.61.0 added a deprecation warning for Node.js 20, so plan on Node.js 22.12 or later. Changelog, installation

By default the CLI sends anonymized usage data on each run, including the command, its exit code, the CLI, Node.js and npm versions, the type and version of API description, and the names of lint rules that reported problems. Redocly says file names and URLs are removed. Set REDOCLY_TELEMETRY=off, or telemetry: off in redocly.yaml, to stop it. Usage data

Two 2026 security advisories affect other commands, not lint: a path traversal in split (CVE-2026-63225, fixed in 2.33.2) and code execution from a malicious Arazzo description run with respect (CVE-2026-63325, fixed in 2.33.0). Both affect only files from untrusted sources, and both were fixed in June 2026. The two user reports we cited on October 1, about duplicate parameters with shared path items and a bundling loss, are closed; Redocly’s changelog records fixes in 2.49.1 and 2.45.0. Split advisory, respect advisory, issue #2829, issue #2964

In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Redocly CLI 2.57.0 with --extends=spec reported only the planted path-parameters-defined error in a small broken contract, exited 1, and passed the repaired file. Its default recommended profile failed the repaired public file on its security-declaration rule. Earlier check record, October 1, 2026

The strongest reason not to choose it is the Node.js requirement. If your CI images have no Node.js and you do not want Docker, Vacuum is the better fit.

Used Redocly CLI? Share your experience to help other readers choose.

Vacuum

Also consider · Node-free single binary

$0MIT · no account

Choose Vacuum for a native binary without Node.js, or to run Spectral-style rules without Spectral. Tune its recommended rules for a first gate and pin the version, because one developer maintains it and it changes quickly.

Reasons to choose it

  • Single binary via Homebrew, script, Docker or Go
  • Documented exit codes, including 2 for a rule timeout
  • Loads Spectral-style YAML and JSON rulesets within documented limits

What to watch

  • One main maintainer; pre-1.0 with frequent changes
  • No spec-only ruleset; defaults also fail missing descriptions and operation IDs
  • Official Action fails below a quality score of 70 by default

Vacuum is a Go program distributed as a single binary through a Homebrew cask, a shell installer, Docker images for amd64 and arm64, and go run. An npm wrapper also exists; it downloads the binary at install and needs Node.js 24.16 or later. Without a ruleset it applies its recommended OpenAPI rules, and --fail-severity (default error) sets what fails the run. Its documented exit codes are 0 for no violations at or above that threshold, 1 for violations, and 2 for a parsing, file, flag or other tool error. In the current release, a rule or lookup that times out also returns 2, and the README says a timeout “is an incomplete check, not evidence that the document is clean”. Defaults are 5 seconds per rule and 500 milliseconds per lookup. README, lint options, exit codes

Vacuum has no separate specification-only ruleset. Its recommended rules mix structure with documentation conventions: its source marks path-params, operation-operationId and info-description all as recommended errors. A team that wants a purely structural first gate writes its own ruleset or switches some rules off. It loads Spectral-style YAML and JSON rulesets, with compatibility limits listed in its Spectral migration notes, plus custom JavaScript functions, an ignore file, a built-in OWASP ruleset, JSON, Spectral-format and HTML reports, a pipeline summary, a language server and a bundle command. It parses OpenAPI 3.0, 3.1 and 3.2 through its libopenapi library. Rulesets, rule source, libopenapi

Read the full Vacuum analysis and sources

The official GitHub Action, pb33f/vacuum-action@v2, needs a token with permission to comment on pull requests. By default it fails the check below a quality score of 70 as well as on errors, so a contract can fail on style warnings alone. Running the binary directly keeps the gate to the exit codes above. Normal commands also check for a newer release at most every 12 hours; --no-update-check or VACUUM_NO_UPDATE_CHECK=true turns that off. GitHub Action, README

One main maintainer and fast change

Dave Shanley wrote all of Vacuum’s 20 most recent commits and is the only maintainer of its npm package. It had 53 releases between January 1 and October 19, 2026; the October releases added AsyncAPI bundling, Arazzo workflow linting and stricter OWASP checks. On October 19 it had 11 open issues, a small backlog; one open report (#938) describes some rules firing twice non-deterministically. No security advisory has been published for it. A single maintainer is a continuity risk, so pin the version as you would for Redocly. Releases, issue #938, security

In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Vacuum 0.30.6 flagged the planted missing path parameter, a missing operation ID and a missing description as errors and exited 1; the repaired file exited 0 with six style warnings. Earlier check record, October 1, 2026

Choose it if a Node-free binary matters more than a ready-made spec-only ruleset, or if you want to keep Spectral-style rules without running Spectral.

Used Vacuum? Share your experience to help other readers choose.

oasdiff

One binary for validation and compatibility checks

$0Apache-2.0 · no account

Use validate for one contract and breaking for changes between versions. Prefer Redocly for a ready-made structural gate with more custom-rule growth.

Reasons to choose it

  • Native binaries for Windows, macOS and Linux
  • Validates one contract for per-RFC violations
  • Recent fixes improve finding order and completeness

What to watch

  • Less custom governance control than a dedicated linter
  • Use current versions for external-reference security fixes
  • No measured validation accuracy established

Oasdiff is best known for comparing two contract versions, but oasdiff validate openapi.yaml checks a single document for per-RFC violations, including invalid types, missing required fields, bad regular expressions and unresolved references. Its README lists prebuilt binaries for Windows, macOS and Linux, as well as Go, Homebrew and container installation. The Apache-2.0 local command requires no account or paid service. Choose it if you already use oasdiff for compatibility checks and want one installation for both jobs. Repository and commands (checked November 6, 2026).

Version 1.35.0, released October 28, fixes duplicate validation findings being collapsed in JSON specifications and makes validation output deterministic. Its tracker still contains requests about conflicts split across allOf and required read-only or write-only properties. Those reports are useful limits, not measured failure rates. Releases, issue tracker (checked November 6, 2026).

Read the full oasdiff analysis and sources

Its release notes also describe fixes to external-reference controls and git input handling. Use a current pinned version and trusted local contracts. We have not established every advisory’s affected-version range from the summary page, so this is an evaluated alternative rather than a security assurance. It offers less room for custom governance rules than Redocly, Vacuum or Spectral. Security notices (checked November 6, 2026).

Used oasdiff? Share your experience to help other readers choose.

Speakeasy OpenAPI CLI

Configurable multi-file linting in a Go binary

$0MIT · no account

Choose it for native multi-file linting and custom TypeScript rules. Tune its default all ruleset before treating failures as structural defects.

Reasons to choose it

  • Windows, macOS and Linux binaries
  • Multi-file lint with JSON source coordinates
  • Configurable rules and interactive fixes

What to watch

  • Defaults mix structure with style and security policy
  • README does not enumerate exit codes
  • No published security policy

Speakeasy’s MIT-licensed openapi command runs as a Go binary on Windows, macOS and Linux. Its spec lint command handles multi-file contracts directly and can report findings as JSON with source files and coordinates. The maker documents built-in semantic, style, security and schema rules, custom TypeScript rules executed without a Node.js dependency, per-rule overrides and interactive fixes. Choose it for configurable governance and multi-file linting when a native binary matters. Repository, linter announcement (checked November 6, 2026).

The default all ruleset includes security policy, so a public write operation without authentication can fail even when the contract is structurally valid. Choose rules deliberately; recommended and individual rule overrides are documented. The announcement acknowledges gaps in output formats, including SARIF and JUnit, and the README does not enumerate exit codes. Its benchmark claims are the maker’s own and do not decide our recommendation. Linter announcement (checked November 6, 2026).

Read the full Speakeasy OpenAPI CLI analysis and sources

Version 1.26.3 was released November 2. Recent changes include fixes to writing lint corrections, source attribution for referenced documents and schema rules. The security page lists no published advisories and no security policy; that does not prove an absence of vulnerabilities. The local tool needs no hosted account or subscription. Releases, security, MIT license (checked November 6, 2026).

Used Speakeasy OpenAPI CLI? Share your experience to help other readers choose.

Which product are we missing?

Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.

Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.

Suggest a product

Opens an email draft with this article attached as a link. Nothing is sent until you send it.

No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.

What people are saying

Practical Picks has no reader reviews for these tools yet. The public discussion we found is mostly about Spectral’s upkeep. In May 2026 a user asked on Spectral’s tracker whether a new release would land soon so that their organization could evaluate it; a contributor answered that npm tracks recent releases, and no SmartBear reply appears on the issue. In July 2026 the API consultant Kin Lane called Spectral “a project on life support” when he started the API Commons copy; he builds governance tools on its format, so he is not a neutral party. In February 2026 Speakeasy, which sells API tooling and now offers its own open-source linter, called Spectral “largely dormant” and said Vacuum “uses significantly more memory” than its own tool. SmartBear’s August 2026 update said its engineers work on commercial and open-source projects in sprints and that it would continue its stewardship. For Redocly CLI, the two user reports we cited in October are closed with fixes. For Vacuum, the open issues are mainly feature requests. These are individual accounts, not measurements. Spectral issue #2949, Kin Lane, July 29, 2026, Speakeasy, February 9, 2026, SmartBear, August 14, 2026

How we researched

This is public-source research. For this review we did not install or run any of these tools, create accounts or contact a maker. No maker supplied access or payment, and our links carry no affiliate tracking. We first compared these tools and one newer tool on October 1, 2026, including a small hands-on check on a fictional contract. On October 19, 2026 we rechecked documentation, changelogs, release and package records, issue trackers, security advisories and independent reporting, and made the decision again from public evidence.

We wrote this for a small team with an OpenAPI contract in its repository that wants one command to run locally and in CI and to fail a pull request when the contract breaks the specification. The criteria remain gate accuracy and control (30%); setup and CI fit (15%); rules and room to grow (15%); maintenance, security and supply chain (30%); and cost (10%). AI features carry no weight. Redocly CLI scores 4.40, Vacuum 4.03, oasdiff 3.95 and Speakeasy 3.95 out of 5. Redocly remains first when we vary the price emphasis. These are editorial judgments from documentation, not measured accuracy rates.

On November 6, 2026 we examined current repositories, launch coverage, release notes, issue trackers, security notices and the OpenAPI tools directories for newcomers and omitted alternatives. We retained October 19 evidence for incumbent capabilities. Speakeasy’s maker already offered API linting; AuditAPI scores 3.05, but its grade-based policy does not establish the required structural gate. OpenLint now documents npm installation, so an empty GitHub releases page alone does not establish unavailability. Its distinct first release date is unknown; Windows binary availability is also unconfirmed. Scalar CLI first appeared in January 2024, before our two-year newcomer window. Specsanity and OpenSpec were previously identified as web tools; their current local-command availability could not be confirmed. The old API Commons repository returned 404. None of the newcomers we examined qualified for Rising Star. OpenLint, Speakeasy announcement, OpenAPI tools directory, community directory (checked November 6, 2026).

Spectral CLI scores 3.43: it remains the most flexible engine, but its maintenance, dependency-compromise record and default install analytics argue against starting a new gate with it. A fresh install on July 14, 2026 could pull a compromised AsyncAPI dependency; Spectral 6.16.3 pinned a safe version on August 3. Since June 2026 its npm packages report installations to Scarf unless you opt out with SCARF_ANALYTICS=false or DO_NOT_TRACK=1. Dependency records also place malicious versions published November 24, 2025 within Spectral’s declared range; that earlier exposure is inferred from those records, rather than confirmed by SmartBear. If you installed on either date, check the advisory and its indicators of compromise. Pin versions and install from a lockfile for future runs. SmartBear update, OSV advisory, Scarf opt-out (checked October 19, 2026). OpenLint scores 3.88: it offers extensible rules, but Windows binary availability and clean JSON output have unresolved reports. OpenLint issues, installation (checked November 6, 2026). IBM OpenAPI Validator scores 3.88; its Spectral-compatible rules and native binaries are useful, but IBM conventions add configuration for this reader. Oasdiff ranks ahead of Speakeasy at their equal total on maintenance, security and supply chain. Openapi-spec-validator scores 3.73; it suits Python pipelines but offers less custom-rule growth and structured CI output. OpenAPI Generator’s validate command scores 3.50, with Java setup and less governance control. Scalar CLI scores 3.80: it supports local validation and Spectral linting, with Windows and macOS standalone installers. Its local commands are free under the repository’s MIT licence; authentication is for Scalar services. Scalar CLI, Scalar licence, IBM, Python validator, OpenAPI Generator usage (checked November 6, 2026).

Optic and Swagger CLI have archived repositories. Zally requires a server; Swagger Parser and libopenapi are libraries rather than standalone gate commands. Hosted governance services require accounts. Those are concrete reasons to choose a different option for this local command-line job. Optic, Swagger CLI, Zally, Swagger Parser, libopenapi (checked November 6, 2026).

ToolPublic sourcesWhat remains uncertain
oasdiffRepository, commands, releases, issue tracker and security notices, checked November 6, 2026.Exact advisory applicability and custom governance limits; no measured validation accuracy.
Speakeasy OpenAPI CLIRepository, February launch article, MIT license, releases, issues and security page, checked November 6, 2026.Exact exit codes; independent benchmark replication; no published security policy.
Newer alternativesOpenLint, AuditAPI, Scalar and discovery directories, checked November 6, 2026.OpenLint distinct first release date and Windows binaries; Scalar lint-package advisory applicability; current Specsanity and OpenSpec local-command availability.
Redocly CLILint, ruleset, spec-ruleset, installation, CI and usage-data documentation; changelog; npm package record; repository, license and security advisories; generate-spec page; closed issues #2829 and #2964.Exact exit-code values (the lint reference does not list them); how often rule additions break existing pipelines in practice.
VacuumREADME, lint, exit-code, ruleset and GitHub Action documentation; rule source; release and commit feeds; npm package record; open issues; security page; libopenapi README.Continuity with one main maintainer; how fully Spectral rulesets carry over; behavior on very large contracts near the timeouts.
Spectral CLIREADME, CLI guide, OpenAPI rules, license, package changelogs and npm records, release feed, issues #2729, #2949, #2999 and #3069, SmartBear’s August 2026 update, OSV record MAL-2025-190643, Scarf package documentation, fork repositories and commentary.SmartBear’s plans for the project; whether a community fork will release; which release added OpenAPI 3.2.

The October 1 check covered one fictional OpenAPI 3.0.3 file with a missing path parameter and a repaired control, on Linux. It is kept as dated history and did not decide the Pick. Nothing here establishes speed, behavior on large multi-file contracts or real CI reliability. Next substantive review is due January 17, 2027, or sooner if newcomer availability is confirmed, Vacuum reaches 1.0 or a security advisory appears. Found a changed release or a fix? Contact the editors.

Sources and evidence

Checked October 19, 2026:

Additional sources checked November 6, 2026: oasdiff releases, Speakeasy releases, OpenLint installation, OpenLint CLI, Scalar CLI, Scalar licence. Incumbent capability and historical security findings above retain their October 19 check date.