-
Currently the help shows the following:
```
omar@omar:~$ openVulnQuery -h
usage: openVulnQuery [-h] (--cvrf | --oval)
(--all | --advisory API_RESOURCE | --cve API_RESOURCE | --latest API_RESOURC…
-
Documentation in the help (-h) option should be made a little more clear.
For instance:
` --advisory API_RESOURCE | --cve API_RESOURCE | --latest API_RESOURCE | --severity API_RESOURCE | --year …
-
Since the openVuln API now has all the additional fields that we used to parse from CVRF, please remove the need of parsing CVRF and the dependency from lxml.
-
Product search should not be dependent on other arguments, such as "--all --advisory --cve --latest --severity --year is required"
According to the openVulnQuery documentation the product search c…
-
I would like to suggest that we try to enhance the Product Tree schema/model.
The intent is to support more automation for (examples of use cases):
1) Automated generation of OVAL content
2) Automa…
-
Since the addition of the new fields on the API the table (human readable) is not appropriate anymore. Please change the client to only display the json results from the API.
The user can still se…
-
Minor issue, but results headers are incorrect in the table.
```
omar@ares:~$ openVulnQuery --cvrf --latest 1 -f advisory_id sir cves advisory_title
+-------------------------+----------+--------…
-
We should host [CVRF](http://www.icasi.org/the-common-vulnerability-reporting-framework-cvrf-v1-1/) data about the vulnerablities in the database so that it can be consumed by organizations such as NI…
-
Here is a report from the oss-security mailing list for [Vulnerability Roundup 27](https://github.com/NixOS/nixpkgs/issues/24319).
[Skip to First Email](#first-email)
# Instructions:
## Identificati…
-
Getting the following error in csv function due to special character encoding.
```
root@psirt-saint:~# openVulnQuery --cvrf --all --csv all.csv
Traceback (most recent call last):
File "/usr/lo…