[ https://issues.apache.org/jira/browse/HADOOP-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299139#comment-15299139 ]
Larry McCay commented on HADOOP-13198: -------------------------------------- I think that precommit would be great. No one should be able to commit a change that introduces a new vulnerable dependency. Would it be possible to make that the criteria? Only block new dependencies that have vulnerabilities? Then periodic runs for existing dependencies could have a bounty for showing progress per release or something like that? Zero vulnerabilities would be too much especially in the beginning. > Add support for OWASP's dependency-check > ---------------------------------------- > > Key: HADOOP-13198 > URL: https://issues.apache.org/jira/browse/HADOOP-13198 > Project: Hadoop Common > Issue Type: Improvement > Components: build > Reporter: Mike Yoder > Assignee: Mike Yoder > Priority: Minor > Attachments: HADOOP-13198.001.patch, > hadoop-all-dependency-check-report.html > > > OWASP's Dependency-Check is a utility that identifies project > dependencies and checks if there are any known, publicly disclosed, > vulnerabilities. > See https://www.owasp.org/index.php/OWASP_Dependency_Check > This is very useful to stay on top of known vulnerabilities in third party > jars. Since it's a maven plugin it's pretty easy to drop in. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org