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
I'd rather use published_timestamp to only feed data that has been published. Generally, published data should be considered with a higher confidence level than non-published one.
The text was updated successfully, but these errors were encountered:
I would tend to agree with you if we were expecting data to published. In many cases, there are many automatic event adding vulnerability attributes with a timestamp which is the closer timestamp to the actual sighting. Maybe we could have the option in the tool to decide what to take depending of the use-case.
VulnerabilityLookupSighting/vulnerabilitylookupsighting/publish.py
Line 99 in cf3a1cd
I'd rather use
published_timestamp
to only feed data that has been published. Generally, published data should be considered with a higher confidence level than non-published one.The text was updated successfully, but these errors were encountered: