Fixes #41 #
Add extra validation checks to make sure there are no unexpected properties in CVSS.
Types of changes
What types of changes does your code introduce to CvssSuite?
Put an x in the boxes that apply
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR.
[x] Unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
Further comments
Depending on the behaviours that people use this suite for, it might break some CVSS vectors that were considered valid even though they were not. That's why I marked it as breaking change.
Proposed changes
Fixes #41 # Add extra validation checks to make sure there are no unexpected properties in CVSS.
Types of changes
What types of changes does your code introduce to CvssSuite? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR.Further comments
Depending on the behaviours that people use this suite for, it might break some CVSS vectors that were considered valid even though they were not. That's why I marked it as breaking change.