OpenLint 1.0.0 is on npm, the specification is published, and the docs are live. The next step is the one that matters most to anyone running Spectral today: moving over. We’re looking for beta testers to help us prove that path.
API Commons has switched
API Commons runs a stack of API governance tools on the linter, including validator.apicommons.org, a governance MCP server and a catalog of more than 700 rules. All of them now run on OpenLint. We checked the results against Spectral 6.16.1 on every fixture we have, and they matched.
The move was mostly a rename. What tripped us up is what we want to hear about from you:
- Custom functions that import Spectral’s core. A function that imports
@stoplight/spectral-corewon’t load in OpenLint. Import from@openlint/openlint-coreinstead, and use named imports rather than a default import. - Extra metadata on rules. Rulesets that carry their own properties, such as a title or a prompt for an AI agent, are rejected, so we strip them from published rulesets for now.
- JSON output on a clean run. With
-f json, a run with no problems prints[]plus a line of text, which a script parsing the output has to allow for.
These are in front of the community, and backwards compatibility is the subject of an open discussion.
How to migrate
The Spectral migration guide has the details. For most teams it’s two steps:
- Install OpenLint:
npm install openlint, or run it withnpx openlint lint. - Change
spectraltoopenlintin your commands and pipelines.
Your existing .spectral.yaml and extends: spectral:oas keep working. If you use the JavaScript API, the guide shows how to alias the old package names so you can try OpenLint without changing any code, and how to rename things properly when you’re ready.
Help us test it
We want companies, organizations, institutions and government agencies of every size to try the migration on their real rulesets and pipelines: custom functions, shared rulesets pulled over the network, CI setups, and editor workflows.
If you’d like to take part:
- Tell us you’re testing. Email [email protected] or start a thread in Discussions. Just knowing who’s trying it helps us decide what to fix first.
- Report what breaks. Anything that behaves differently from Spectral, or anything the guide doesn’t cover, goes in an issue on openlint/openlint.
- Come to office hours. We meet every Thursday at 9:00 ET. Agendas are in openlint/community, and recordings and transcripts are on this site.
We’re aiming to make the official launch at API Days Paris, and we’d like to go in with migration stories from more than one organization. If yours could be one of them, we’d love to hear from you.