A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Why I Forked Spectral, And Why It Became OpenLint," Kin Lane, October 27, 2026, https://apievangelist.com/2026/10/27/why-i-forked-spectral-and-why-it-became-openlint/
Marisol was eating lunch at her desk when the post came through, and she nearly skipped it. She was a platform engineer, and the linting rules for her company's APIs lived in a single file in a Git repository that she had written, mostly alone, over two years. Developers got it through a VS Code plugin and a CI step. Nothing else carried it anywhere.
The line that stopped her was about the format itself. The author says it was never specified and that "It is whatever the Spectral CLI happens to do." She read it twice. Her stomach dropped a little, because it described her situation exactly. Her whole governance effort rested on behavior nobody had ever written down. When a rule misfired last spring, she had fixed it by trial and error and never found out why it had broken.
She did not agree with all of it. The author admits the name OpenLint is not the one they would have picked, and Marisol found that mildly funny, but the weekly office hours and the Open Collective sounded to her like a lot of meetings and a request for money. She had enough of both. She also noticed that the post says very little about what happens to teams who simply stay on Spectral and wait. The project says it wants existing rulesets to keep working, which she wanted to believe, and she kept a small, stubborn doubt anyway. Promises made in a blog post cost nothing. Her budget for adopting something new was close to zero.
Still, one passage kept pulling her back. The author wrote that a fork only one company maintains "is the same problem Spectral has, with a different name on it." She had built something like that herself, a private fork of conventions maintained by exactly one person, and she knew who that person was. She was uncomfortable with the comparison, and she also thought it was fair.
What interested her most was the distribution problem. The author says most teams have no way to version, update or evolve their rules across teams, beyond Git and a plugin. Marisol had been calling that a personal failing, as if a better engineer would have solved it. Reading that other companies had the same itch did not fix anything, but it made her feel less foolish.
She was not going to rewire her pipeline over lunch, and she did not want to join a call just to listen. The post said the draft specification records, inline, every place where behavior had to be reverse-engineered from Spectral. That seemed like something she could check on her own, with no commitment.
So she opened the specification at spec.openlint.org in a second tab. She kept her ruleset beside it and picked the two custom rules she trusted least, the ones she had never been able to explain to a new hire. She searched the draft for anything touching them. She had no idea whether she would find anything.
Then she made a note in the README of her rules repository: check these two rules against the draft, and write down what it says. She hit save and went back to her sandwich.