Skip to content
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

Add publication/modification/withdrawn date information to vuln records #2259

Closed
2 of 13 tasks
wagoodman opened this issue Nov 14, 2024 · 1 comment
Closed
2 of 13 tasks

Add publication/modification/withdrawn date information to vuln records #2259

wagoodman opened this issue Nov 14, 2024 · 1 comment
Labels
enhancement New feature or request planning high level epic that should be broken into smaller tasks

Comments

@wagoodman
Copy link
Contributor

wagoodman commented Nov 14, 2024 •
edited
Loading

Today the v6 DB schema effort is adding date record publication/modification/withdrawn information to the schema. When this lands we can start hydrating these fields in grype-db and vunnel based on the available information in the upstream vulnerability data. This is a high-level tracking issue for this work.

Vunnel work:

  • Allow for date information to be added to the OS workspace schema schemas version 2 wishlist vunnel#266
  • Update debian provider Track published/modified date for debian data vunnel#732
  • Update rhel provider
  • Update mariner provider
  • Update chainguard provider
  • Update wolfi provider
  • Update amazon provider
  • Update oracle provider
  • Update sles provider
  • Update ubuntu provider
  • Update alpine provider
  • Update github provider this is based on OSV which already has these fields and the v6 work will plumb this through to the DB 🎉
  • Update NDV provider this is based on OSV which already has these fields and the v6 work will plumb this through to the DB 🎉
@wagoodman wagoodman added enhancement New feature or request planning high level epic that should be broken into smaller tasks labels Nov 14, 2024
@wagoodman wagoodman mentioned this issue Nov 14, 2024
Open
@wagoodman
Copy link
Contributor Author

The fields have already been added to the v6 schema and all remaining work is in vunnel -- we'll track this over there anchore/vunnel#742

@wagoodman wagoodman closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2024
@github-project-automation github-project-automation bot moved this to Done in OSS Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request planning high level epic that should be broken into smaller tasks
Projects
OSS
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wagoodman