DependencyCheck - OWASP dependency-check is a software composition a

项目说明

![Ma]() ![Build and Deploy Snapshot]() ![CII Best Practices]() ![Apache 2.0 License]()

![Black Hat Arsenal]() ![Black Hat Arsenal]() ![Black Hat Arsenal]() ![Black Hat Arsenal]()

Dependency-Check

Dependency-Check is a Software Composition Analysis (SCA) tool that attempts to detect publicly disclosed contained within a project's dependencies. It does this by determining if there is a Common Platform Enumeration (CPE) identifier for a gi. If found, it will generate a report linking to the associated C.

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].

Notice

This product uses the NVD API but is not endorsed or certified by the NVD.

Mandatory Upgrade to 12.1.0+

Due to NVD API compatibility changes, an upgrade is mandatory. See #7463 for more information.

Breaking Changes in 11.0.0

Java 11 is now required to run dependency-check 11.0.0 or higher

H2 database upgrade

11.0.0 contains breaking changes using the local H2 database. A full download
of the NVD data will occur. Note that if you are using a shared data directory
the h2 database file is not compatible with older of dependency-check.
If you run into problems you may need to run a purge:

- gradle: ./gradlew dependencyCheckPurge
- maven: mvn org.owasp:dependency-check-maven:11.0.0:purge
- cli: dependency-check.sh --purge

Other notices

NVD API Key Highly Recommended

Dependency-check moved from using the N to the NVD API since 9.0.0+ (January 2024).
Users of dependency-check are highly encouraged to obtain an NVD API Key; see
Without an NVD API Key dependency-check's updates will be extremely slow.
Please see the documentation for the cli, maven, gradle, or ant integrations on
how to set the NVD API key.

#### The NVD API Key, CI, and Rate Limiting

The NVD API has enforced rate limits. If you are using a single API KEY and
multiple builds occur you could hit the rate limit and receive 403 errors. In
a CI en one must use a caching strategy.

Sonatype OSS Index mandatory authentication and migration to Sonatype Guide

In September 2025 Sonatype OSS Index started enforcing use of API tokens for authentication. In April 2026 a
subsequent migration to Sonatype Guide began, kicking off a transition to use of Sonatype Guide API Tokens that are
planned to replace the legacy OSS Index API keys/tokens before the end of 2026.

Without credentials, Dependency Check will automatically disable the OSS Index analyzer. Please see the documentation
for the CLI, Maven, Gradle, or Ant integrations on how to set the analyzer credentials for use of a Sonatype Guide token
or legacy OSS Index API key.

If you wish to use Sonatype OSS Index () you must configure Dependency-Check and consider implications for the
migration to Sonatype Guide; whose commercial/usage model has changed. See the analyzer documentation
for more information.

Gradle build En

With 9.0.0+ users may encounter issues with NoSuchMethodError exceptions due to
dependency resolution. If you encounter this issue you will need to pin some of
the transiti of dependency-check to specific . For example:

/buildSrc/build.gradle

Requirements

Ja

Minimum Ja: Java 11

Internet Access

OWASP dependency-check requires access to several externally hosted resources.
For more information see Internet Access Required.

Build Tools

In order to analyze some technology stacks dependency-check may require other
de tools to be installed. Some of the analysis listed below may be
experimental and require the experimental analyzers to be enabled.

1. To analyze .NET Assemblies the dotnet 8 run time or SDK must be installed.
- Assemblies targeting other run times can be analyzed - but 8 is required to run the analysis.
2. If analyzing GoLang projects go must be installed.
3. The analysis of Elixir projects requires mix_audit.
4. The analysis of npm, pnpm, and yarn projects requires npm, pnpm, or yarn to be installed.
- The analysis performed utilize the respective audit feature of each.
5. The analysis of Ruby is a wrapper around bundle-audit, which must be installed.

Current Releases

Jenkins Plugin

For instructions on the use of the Jenkins plugin please see the OWASP Dependency-Check Plugin page.

Command Line

More detailed instructions can be found on the
dependency-check github pages.
The latest CLI can be downloaded from github in the releases section.

Downloading the latest release:

On *nix

On Windows

On Mac with Homebrew
Note - homebrew users upgrading from 5.x to 6.0.0 will need to run dependency-check.sh --purge.

Ma

More detailed instructions can be found on the dependency-check-ma pages.
By default, the plugin is tied to the phase (i.e. m). Alternatively,
one can directly invoke the plugin via mvn org.owasp:dependency-check-ma.

The dependency-check plugin can be configured using the following:

Gradle Plugin

For instructions on the use of the Gradle Plugin, please see the dependency-check-gradle github page.

Ant Task

For instructions on the use of the Ant Task, please see the dependency-check-ant github page.

De Prerequisites

For installation to pass, you must have the following components installed:
* Java: ja 25.0
* Maven: m 3.6.3 and higher

Tests cases require:
* dotnet core 8.0
* Go: go 1.12 and higher
* Ruby bundler-audit
* Yarn
* pnpm

De 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 listed above be used.

The repository has some large files due to test resources. The team has tried to clean up the history as much as possible.
However, it is recommended that you perform a shallow clone to sa time:

On *nix

On Windows

Then load the resulting 'dependency-check-report.html' into your fa browser.

#### Building without running tests
To speed up your turnaround cycle times, you can also compile without running the tests each time:
mvn -s settings.xml install -DskipTests=true

Please remember to at least run the tests once before opening the PR. :)

IntelliJ Idea

To be able to debug your tests in IntelliJ Idea, you can introduce a ma that executes your test and enables debugging with breakpoints etc.
Basically, you do what´s described in and set the forkCount to 0, otherwise debugging won´t work.

Step by step:

Run -> Edit Configurations

+ (Add new configuration) -> Maven

Give the Configuration a name, e.g. Run tests

Choose working directory, e.g. core

In command line, enter -DforkCount=0 -f pom.xml -s ../settings.xml test

Press OK

Run -> Debug, then choose the newly created run configuration

IntelliJ will now execute the test run for the core subproject with enabled debugging. Breakpoints set anywhere in code should work.

#### Only test one function or one class
If you would like to speed up your turnaround cycle times, you can also just test one function or one test class.
This works by adding -Dtest=MyTestClass or -Dtest=MyTestClass#myTestFunction to the run configuration. The complete command line in the run configuration then would be:

-Dtest=MyTestClass#myTestFunction -DforkCount=0 -f pom.xml -s ../settings.xml test

Docker

In the following example it is assumed that the source to be checked is in the current working directory and the reports will be written to $(pwd)/odc-reports. Persistent data and cache directories are used, allowing you to destroy the container after running.

For Linux:

For Windows:

Building From Source
--------------------

To build dependency-check (using Java 11) run the command:

Running dependency-check on dependency-check
--------------------------------------------

Dependency-check references several dependencies that are never used
except as test resources. All of these optional test dependencies are included in
the test-dependencies profile. To run dependency-check against itself simple
exclude the test-dependencies profile:

Building the documentation
--------------------------

The documentation on the github pages is generated from this repository:

mvn -s settings.xml site site:stage

Once done, point your browser to ./target/staging/index.html.

Building The Docker Image
-------------------------
To build dependency-check docker image run the command:

License
-------

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.

This product includes or consumes third party software. Please see the [NOTICE.txt][notices] file for more information.

This product uses the NVD API but is not endorsed or certified by the NVD.

Copyright (c) 2012-2026 OWASP Dependency-Check Contributors. All Rights Reserved.

[wiki]:
[notices]:

<img referrerpolicy="no-referrer-when-downgrade" src=" />

项目信息

开发语言：Java

Star 数：7716

技术要点

该项目属于漏洞知识库方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕OWASP dependency-check is a software composition analysis utility that detects publicly disclosed vulnerabilities in application dependencies.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。