You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With 9.0.0 dependency-check has moved from using the NVD data-feed to the NVD API. Users of dependency-check are highly encouraged to obtain an NVD API Key; see https://nvd.nist.gov/developers/request-an-api-key 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.
27
+
28
+
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 environment one must use a caching strategy or an external database updated with a scheduled weekly job
29
+
26
30
#### Publisher
27
31
The publisher works independently of the tool configuration or builder and is responsible for reading dependency-check-report.xml and generating metrics, trends, findings, and optionally failing the build or putting it into a warning state based on configurable thresholds.
With 9.0.0 dependency-check has moved from using the NVD data-feed to the NVD API.<br>
4
+
Users of dependency-check are <b>highly</b> encouraged to obtain an NVD API Key;
5
+
see https://nvd.nist.gov/developers/request-an-api-key<br>
6
+
Without an NVD API Key dependency-check's updates will be <b>extremely slow</b>.
7
+
</p>
8
+
<p>
9
+
<b>The NVD API Key, CI, and Rate Limiting</b><br>
10
+
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.<br>
11
+
<u>In a CI environment one must use a caching strategy or use a set API KEY to use for different jobs.</u>
0 commit comments