Roberto Polli

WIP: design support rules.

1

## This PR - includes some design rules

## I expect - more rules for readability

Switch to spectral 6.x

1

## This PR - [ ] updates to spectral 6.x - [ ] migrate rules (stalled, waiting for 6.1 which should fix a regression in merge keys) Fixes #348

## I expect To block processing problematic files: - [ ] binary files  - [ ] files containing tabs '\t' - [ ] the tab characters to be highlighted...

## I expect to selectively disable rules via a `# noqa` comment or flagging them in the GUI NB: SEE spectral 6.0.0 behavior before implementing ## Instead I can't ##...

## I expect to support OAS3-1 stuff in rules, eg. - [ ] MUST info.summary - [ ] MUST info.license.identifier ## Notes - This requires spectral 6.x

## I wish to consider some security hints stated here. - [ ] https://apisecurity.io/encyclopedia/content/oasv3/oasv3_audit.htm - [ ] https://github.com/shieldfy/API-Security-Checklist - [ ] missing required properties hint @berez23 Please file a list...

## Note Consider adding a rule to check for common [redos](https://en.wikipedia.org/wiki/ReDoS) patterns in regexp. The analysis shouldn't probably go that far, but some patterns (eg `*)*` are easy to find)....

## I wish - to identify a score 0-100 mechanism to evaluate API compliance; - the score depends on the issue level (info, warning, error); - security and compliance should...