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
{{ message }}
This repository was archived by the owner on Nov 26, 2024. It is now read-only.
-**wait**: tells if we should wait between NVD API calls to ensure that we are below rate limits
115
117
-**strict**: tells if we should consider vulnerability matches without version as matching dependency
118
+
-**ignore**: a list of CVE vulnerabilities to ignore
116
119
-**memcachier** is the configuration for *memcachier*, see below
117
120
-**memcached** is the configuration for *memcached*, see below
118
121
-**file** is the configuration for *file* cache, see below
119
-
-**ignore**: a list of CVE vulnerabilities to ignore
120
122
121
123
You can also set NVD API Key in your environment with variable *NVD_API_KEY*. This key may be overwritten with value in configuration file. Your API key must be set in environment to be able to run integration tests (with target *integ*).
122
124
123
125
Note that without API key, you will be limited to *10* requests in a rolling *60* second window while this limit is *100* with an API key.
124
126
125
127
## Cache
126
128
127
-
A cache is useful because if you perform more call to NVD database than allowed, your calls will significantly slow down. Gobinsec tries to build caches in this order:
129
+
A cache is useful to limit NVD API calls. If you perform more call to NVD database than allowed, your calls will significantly slow down or you will get status code *403* calling the API.
0 commit comments