dependency-check/DependencyCheck

Support for NIST 2.0 data feeds

クローズ

#7,514 opened on 2025/03/10

 (8 件のコメント) (0 件のリアクション) (0 人の担当者)Java (1,419 件のフォーク)github user discovery
documentationenhancementgood first issuehelp wanted

Repository metrics

Stars
 (7,664 個のスター)
PR merge metrics
 (平均マージ 5d 11h) (30d で 2 merged PRs)

説明

Is your feature request related to a problem? Please describe. The current usage of NIST 2.0 APIs causes issues in some corporate environments, such as air-gapped.

Describe the solution you'd like Using the NIST data feed is much easier to handle in such an environment as creating an mirror of the feeds is easier than "api-mirror". NIST has recently announced (see https://www.nist.gov/itl/nvd) that they will support 2.0 data feeds in parallell with the 2.0 APIs. So the possibility to use the new 2.0 data feeds instead of the 2.0 APIs would we great!

Describe alternatives you've considered An alternative solution could be to set up an internal centralized vuln database which we create from the data feeds, and have dep-check use that database. However, that would require centralized management instead of just creating a self-contained container image.

Additional context n/a

コントリビューターガイド