You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pr@cassandra.apache.org by GitBox <gi...@apache.org> on 2021/09/22 16:38:51 UTC

[GitHub] [cassandra-builds] smiklosovic commented on pull request #57: add dependency check stage into pipeline

smiklosovic commented on pull request #57:
URL: https://github.com/apache/cassandra-builds/pull/57#issuecomment-925097441


   Hi @annubiz, thanks for showing the interest.
   
   what I would do is that I would run it everytime, it does not take a lot of time and it makes things simpler. The way I would like to do this is to fail the build when there is some CVE found.
   
   Right now, there are CVEs found but some of them are false positives (I havent dug into this deeply yet). There is a feature to actually supress these false positives so ideally we should have a clean report and we should fail the build when new vulnerability is found or if a developer introduces a dependency which is vulnerable by means of 'failBuildOnCVSS' from the configuration below (1)
   
   I am afraid that if we dont run this regularly, it will be (maybe) run upon a release and it might be already late - it might be problematic to change the code depending on a library which is vulnerable and so on so I would go with the detection of vulnerabilities as soon as possible so we may react more promptly.
   
   WDYT?
   
   (1) https://jeremylong.github.io/DependencyCheck/dependency-check-ant/configuration.html


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org