Home / Companies / Speakeasy / Blog / Post Details
Content Deep Dive

Why We Built Our Own OpenAPI Linter (And How It Compares)

Blog post from Speakeasy

Post Details
Company
Date Published
Author
Tristan Cartledge
Word Count
4,069
Company Posts That Month
17
Language
English
Hacker News Points
-
Post removed?
No
Summary

APIs are crucial to modern software, and as OpenAPI specifications grow in complexity, existing linters like Spectral and Vacuum face performance challenges with large specs. Spectral, while popular, struggles with scale and requires Node.js, whereas Vacuum, although faster and Go-native, consumes more memory. In response, Speakeasy developed its own OpenAPI linter, part of their openapi CLI, aiming for a balance of speed, memory efficiency, and thoroughness. Their linter, built on a Go library, outperforms alternatives in benchmarks, finding more issues while using less memory and maintaining no runtime dependencies. Despite having fewer built-in rules and output formats, it excels in handling large specs efficiently. Speakeasy's linter reflects a commitment to ongoing development, seeking user feedback to improve its ecosystem and expand its rule set.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Serverless 2 819 177 83 +16%
Developer Experience 1 408 220 96 -1%
Kubernetes 1 1,380 245 88 +48%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.