dependency-check/DependencyCheck

Support for NIST 2.0 data feeds

已關閉

#7,514 建立於 2025年3月10日

 (8 則留言) (0 個反應) (0 位負責人)Java (1,419 個分叉)github user discovery
documentationenhancementgood first issuehelp wanted

倉庫指標

星標
 (7,664 顆星)
PR 合併指標
 (平均合併 5天 11小時) (30 天內合併 2 個 PR)

描述

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

貢獻者指南