Resolve "Consistency Check of Advisory Database Entries"
I integrated a couple of additional checks in the automated sanitisation tool (https://gitlab.com/gitlab-org/security-products/advisory-db-curation-tools/tree/master) which applied the following changes:
-
rename identifier
tosource_identifier
(as discussed in https://gitlab.com/gitlab-org/security-products/advisory-db-curation-tools/issues/2) -
consistently quote affected_range
-
automatically generate the content of affected_version
fromaffected_range
to avoid internal inconsistencies (between the content of the fieldsaffected_version
andaffected_range
) and to provide kind of a template on which the user can rely on when reading the version information
Edited by 🤖 GitLab Bot 🤖