69ebb53a05
commit 1d1a06a5ae7ea4f6e3adbf5a4b8163eba50562a3 Author: Will Stranathan <will@thestranathans.com> Date: Wed Mar 26 22:59:15 2014 -0400 Updated unit tests and logging commit bb00174e62c9657809d6e5a9cde7c7308d905593 Author: Will Stranathan <will@thestranathans.com> Date: Wed Mar 26 22:20:28 2014 -0400 Updated GrokAssembly to not fail if the vendor can't be gotten commit 27f7c9366acca8abbff9c6e9fa9ce1a1329da887 Author: Will Stranathan <will@thestranathans.com> Date: Wed Mar 26 22:18:33 2014 -0400 Updated unit test to not care about version number Former-commit-id: e700a5f81b7b0f6d6ccf392e846723e67fff591c
Dependency-Check
Dependency-Check is a utility that attempts to detect publicly disclosed vulnerabilities contained within project dependencies. It does this by determining if there is a Common Platform Enumeration (CPE) identifier for a given dependency. If found, it will generate a report linking to the associated CVE entries.
Documentation and links to production binary releases can be found on the github pages. Additionally, more information about the architecture and ways to extend dependency-check can be found on the wiki.
Current Releases
Jenkins Plugin
For instructions on the use of the Jenkins plugin please see the Jenkins dependency-check page.
Command Line
More detailed instructions can be found on the dependency-check github pages. The latest CLI can be downloaded from bintray's dependency-check page.
On *nix
$ ./bin/dependency-check.sh -h
$ ./bin/dependency-check.sh --app Testing --out . --scan [path to jar files to be scanned]
On Windows
> bin/dependency-check.bat -h
> bin/dependency-check.bat --app Testing --out . --scan [path to jar files to be scanned]
Maven Plugin
More detailed instructions can be found on the dependency-check-maven github pages. The plugin can be configured using the following:
<project>
<build>
<plugins>
...
<plugin>
<groupId>org.owasp</groupId>
<artifactId>dependency-check-maven</artifactId>
<version>1.0.2</version>
<executions>
<execution>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
...
</plugins>
...
</build>
...
</project>
Ant Task
For instructions on the use of the Ant Task, please see the dependency-check-ant github page.
Development Usage
The following instructions outline how to compile and use the current snapshot. While every intention is to maintain a stable snapshot it is recommended that the release versions listed above be used.
Note, currently the install goal may take a long time to execute the integration tests. However, if this takes more then 30 minutes it is likely that the download of data from the NVD is having an issue. This issue is still being researched and a solution should be published soon.
On *nix
$ mvn install
$ ./dependency-check-cli/target/release/bin/dependency-check.sh -h
$ ./dependency-check-cli/target/release/bin/dependency-check.sh --app Testing --out . --scan ./src/test/resources
On Windows
> mvn install
> dependency-check-cli/target/release/bin/dependency-check.bat -h
> dependency-check-cli/target/release/bin/dependency-check.bat --app Testing --out . --scan ./src/test/resources
Then load the resulting 'DependencyCheck-Report.html' into your favorite browser.
Mailing List
Subscribe: [dependency-check+subscribe@googlegroups.com] subscribe
Post: [dependency-check@googlegroups.com] post
Archive: google group
Copyright & License
Dependency-Check is Copyright (c) 2012-2014 Jeremy Long. All Rights Reserved.
Permission to modify and redistribute is granted under the terms of the Apache 2.0 license. See the LICENSE.txt file for the full license.
Dependency-Check makes use of several other open source libraries. Please see the [NOTICE.txt] notices file for more information.