Pidgey

do you have a link to a file we can parse to get this info?

This makes me thing we should integrate a "last known good" into the VIA4 generation. When a source fails, it can pull the last-known-good. The date could be part of...

I actually recently checked the xml feeds we use, and couldn't find the CVSS v3 score in there. Is there another feed?

We're using: https://static.nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-modified.xml.gz

The reason this is not implemented, is because exploitDB changed their format recently. We didn't want to integrate it yet, while the format was broken. [This has been reported](https://github.com/toolswatch/vFeed/issues/42) to...

Adding this information would conflict with the way CVE-search automates the displaying of information. If we start making rules like this, to check for specific database keys, to then add...

Hello @westlifezs. Yes, this process might take a while. We've had this question before, on our main branch. ( https://github.com/cve-search/cve-search/issues/88) Can you verify if your issue is not a similar...

@toolswatch What would be the preferred approach for CVE-Search?

Decompressing is not an issue. It's more the question of, "does every user of CVE-Search need an account, or do we make one generic account?"

@adulau I assume we should change vFeed to a plug-in as well then, so that users that don't want to create an account, don't have to?