-
Notifications
You must be signed in to change notification settings - Fork 574
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.
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
add createdAt or updatedAt for vulnerabilities scheme #1498
Comments
Thanks for the suggestion @tomerse-sg! I've added this to the "schema version 6 wish list" over at anchore/grype-db#108. Bumping the schema of the database grype uses is a bit of a heavy lift right now, but we're looking at ways to make it easier, and discussing what should be included in the next version (hence the "version 6 wish list"). I've you like to be part of the discussion, feel free to join the community meeting at https://github.com/anchore/grype/#join-our-community-meetings, or ping us on Slack (I think you're already in the slack). |
hi, from your experience, what is the approximate estimation time for the schema version 6 wish list? |
Hi @tomerse-sg, Sorry, but we don't have a time estimate right now for the v6 schema wish list, or even know exactly what the final implementation will look like. If you're interested in working with us on it, please let us know! |
it can be useful. make the DB stateful. will it be added to the v6 db plan? @willmurphyscode |
@tomerse-sg yes, this will be in grype db schema v6 for providers that we can easily get the data from. |
For NVD and GHSA this will be in the DB v6 work, which is in progress now. I expect PRs that implement this to land soon, but we won't switch to using the v6 schema for probably another 2 months (+/- a margin). |
great news! @wagoodman |
great! @wagoodman |
What would you like to be added:
vulnerabilities from NVD and GHSA contains sometimes modification and creation time.
is it possible to add it into the scheme of grype?
Why is this needed:
full information on CVEs \ GHSA\s
Additional context:
The text was updated successfully, but these errors were encountered: