Hi Duminda,
great you like the plugin. Beyond 200 dependent components we recommend you talk to our sales reps and purchase our products ;-). There you find no limit and also more detailed information about the security vulnerabilities that your application faces.
Well, apparently your company already became a customer of the Black Duck Suite. In the Black Duck suite we offer two Jenkins-CI plugins:
* To automate the (source) code scanning with Protex as part of your build (pipeline) in Jenkins. You are correct Protex does not include references to Vulnerabilities, it also does scan only the code you present to it (in a folder). In case of a maven build the dependencies are outside of that build folder (in your shared .m2 repo (cache)
* To automate Code Center our component governance offering, there is a second commercial plugin for Jenkins-CI. It does essentially the same thing as this one, listen to a Maven/Gradle build, compare it against the our KB for vulnerability information. The main differences are that Code Center will catalog your "Bill of Materials" permanently for the build target (called in Application in Code Center) and runs your component requests through a workflow for approval and the ability to stop builds if they are disapproved (i.e. for reason of being vulnerable, ...)
I'd suggest to contact your BD Sales Engineer and clarify if your are using Code Center and how to get the Code Center plugin for Jenkins
Kind regardsKaj