New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

additional affected:ranges entry suggestion #91

Open

kurtseifried opened this issue Oct 12, 2022 · 0 comments

Contributor

kurtseifried commented Oct 12, 2022

So we have

affected:ranges:events:introduced
affected:ranges:events:fixed
affected:ranges:events:last_affected
affected:ranges:events:limit

but we're missing a "notaffected" or "unaffected" as in "we checked and we're not affected at all", e.g. data from the CISA log4j repo:

https://github.com/kurtseifried/log4j-affected-db/blob/develop/data/cisagov.yml

cves:
cve-2021-4104:
investigated: true
affected_versions: []
fixed_versions: []
unaffected_versions: - '>= 1.0.0'

cve-2021-44228:
investigated: true
affected_versions: []
fixed_versions: []
unaffected_versions: - '>= 1.0.0'

So I'd like to propose a "notaffected" tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment