I appreciate your effort here, though, how realistic is the scenario where user gets a swagger.json with properly filled example(s)?

I appreciate your effort here, though, how realistic is the scenario where user gets a swagger.json with properly filled example(s)?

Hi@stamparm . Thanks for your comment. Examples(s) are not required by the swagger spec but it is generally good practice to add them. Adding them has other advantages e.g. Swagger UI will prefill requests from the examples for users browsing and trying your APIs.

It is a small sample size but of the two applications I'm working on in my company, one had full examples already and the other had a handful missing which I was able to add in a few minutes.

If an example is missing a warning is printed and that API is skipped. Other APIs with full examples will still be scanned.

Please add this, it is very useful

Can you please add more description, I want to use it from your repo even though it is not merged

I tried this, it has bugs + there is no document or something that tells how it works + it doesn't directly work when a swagger is supplied + it doesn't run after doing everything(getting rid of bugs).
This needs a lot of improvements and testing.
Thanks for your effort.

While I think you shouldnt find such swagger files in production, I like the idea for security tests while development.