Closed iamamoose closed 1 year ago
Do you have an example of a validation that doesn't have the intended effect?
I thought we created this issue when we saw 'versionType' was not correctly flagged as required, but that seems to work now. That's an 'explicit' form validation and not a schema verification though.
A good example is the Tomcat issue CVE-2022-45143 which failed schema validation (versionType was semver for a single version with no range). vulnogram.github.io correctly flagged this, but we didn't.
our custom/cve5/conf.js validators[] is causing the default/cve5/conf.js validators[] function to not run
fixed, live
default/cve5/conf.js does schema verification that doesn't work, but it does on vulnogram.github.io, so likely I broke something.