Those of you who don’t know about apigeelint, add to your “TO DO” list now, “research apigeelint”. (I recorded a screencast on this about 18 months ago) If you are designing proxies, deploying, running a CI/CD pipeline with API proxy definitions,… Apigeelint is an essential tool. It makes sure your proxies conform to best practices, and don’t include any obvious errors.
For those who DO know apigeelint, I have a short update for you. Today we released apigeelint 2.83.0, which is a small feature update.
Over the last 3 months, we’ve delivered 8 updates with new features and new checks (some driven by customer request), and 2 hotfixes. Over the past year, it is 22 and 6. We stay pretty active and responsive.
The latest update fixes the PO025 plugin, which runs eslint on your JavaScript. In February 2026, eslint released v10, which changes how programs use it. Updating to eslint v10 required changes in apigeelint.
But, because PO025 now uses eslint v10 , if you want to use it, you may need to take action. The key difference is that the configuration files for eslint is now different - it has a different name and a different format. So you may need to update your rules to take advantage of this.
If you don’t specify an eslint config file, apigeelint will apply one for you, automatically and silently. It will apply rules that seems sensible, but they’re not YOUR rules. You should be aware.
More details in the apigeelint README.
That’s all I’ve got. Let me know if you have questions.