[chore]: Adding CVE dependency checks for requirements.txt via pre-commit recommended hooks #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Despite the CVE bogus problem, I think that automatic dependency vulnerability scans is of the essence given the rapid pace of change that the field and its libraries experience. The hook added to the PR direclty checks against safety-db for known vulns. This hook is one of the supported hooks in the pre-commit documentation, present here and seems to me like the no brainer solution for implementing a one shot validation when requirements get updated.
For runs at the time of writing, the requirements established for AIOS show no existent vulnerability.