We'll update the docs to make our dependency on vacuum / spectral clearer - fair feedback. We do more than this though, we also use LLMs to help us identify other issues and recommend fixes.
RateMyOpenAPI is really designed as a quick litmus test to help people get their OpenAPI doc (and thus their documentation) in a good shape quickly, vs the hassle of setting up of individual rules.
People find it quite helpful to quickly build a todolist of things to do with their OpenAPI doc to get it into a much better state.
Co-founder of Zuplo here - we actually created the service to help people get their docs into better shape (we use your OpenAPI to power the dev portal in Zuplo). We find that if folks have a high ratemyopenapi score their docs tend to be pretty good. We have no plans to charge for this service.
Thanks for the feedback, appreciate you taking the time to try it out and comment.
Yeah, some folks might consider going further and use hashes that salted or one-way encrypted via key so that nobody else can recreate the checksum. Some performance tradeoffs but can prevent some other vectors like cache-filling etc.
Author of the article here - look forward to any discussion here. Curious how many folks have already implemented something like this themselves... did you make different decisions?
I agree with all the points made in this, and it reflects my experiences with building an angularJS app. However, I left with a very positive view of angular, technologies should have a learning curve (rather than a learning wall) and angular is my favorite SPA framework for this reason.