OWASP Dependency Track Project

=Main=

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

OWASP Dependency-Track
OWASP Dependency-Track is a Java web application that allows organizations to document the use of third-party components across multiple applications and versions.

Introduction
Over the last several years, organizations have faced a growing trend on the number of vulnerabilities reported due to the use of vulnerable third-party components. The risk involved in using third-party components is described in a paper by Jeff Williams and Arshan Dabirsiaghi titled, "The Unfortunate Reality of Insecure Libraries". This upward trend propelled the use of third-party components into a new category in the OWASP Top Ten, specifically, A9: Using Components with Known Vulnerabilities.

Library Management
Dependency-Track's first goal is to document the use of third-party components across multiple applications and versions. Organizations can document the usage of components including vendors, libraries, versions and licenses. Many organizations have legal or new product introduction requirements that require software engineering teams to provide documentation on the use of third-party components. Dependency-Track aims to meet this requirement.

Vulnerability Management
Coming soon...


 * valign="top" style="padding-left:25px;width:300px;" |

Features
OWASP Dependency-Track can be used to:


 * Hierarchical view of applications and associated versions
 * Document vendors, libraries, versions, and licenses
 * Document dependencies between applications and libraries
 * Provides cross-reference capabilities
 * ...more coming soon...

Presentation
Coming soon.

Download
Coming soon.


 * }

=Screenshots=

= Acknowledgements =

Sponsors
Coming soon.

= Road Map and Getting Involved = As of July 2013, the priorities are:
 * Complete the initial release of Dependency-Track and publish binary and github source repository details
 * Integrate Dependency-Check into Dependency-Track
 * Create dashboard providing at-a-glace visibility into the use of vulnerable components
 * Auto-populate Dependency-Track database with library identification from Dependency-Check
 * Create scheduler to start Dependency-Check scans
 * Update Dependency-Check to use Dependency-Track metadata as the sole source of evidence
 * Translate into other languages
 * Promote use of Dependency-Track

Involvement in the development and promotion of Dependency-Track is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

Localization
Are you fluent in another language? Can you help translate Dependency-Track into that language?

Front-End Gurus
What to provide design or an implementation for a way to visualize data? There's a lot of potential opportunities in this area. Let us know if you can help.

Feedback
Please use the Dependency-Track mailing list for feedback:
 * What you like?
 * What you don't like?
 * What could be improved?

= About Dependency-Track =