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
Capture the dates of each individual providers last successful run in the grype-db metadata.json file
Why is this needed:
So downstream consumers of the published grypedb archive can understand how up-to-date data is for each indvidual provider
Additional context:
Currently any logic that needed to determine how stale vuln data is had to rely on the build date of the grype-db being the first date that any provider failed (which changes with #251 ) or needed access to the raw metadata files of the vunnel workspaces. This will allow for anything that has access to the grypedb archive to have more fine-grained details with per-provider dates and no horrible hacks around the grypedb build date
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Capture the dates of each individual providers last successful run in the grype-db metadata.json file
Why is this needed:
So downstream consumers of the published grypedb archive can understand how up-to-date data is for each indvidual provider
Additional context:
Currently any logic that needed to determine how stale vuln data is had to rely on the build date of the grype-db being the first date that any provider failed (which changes with #251 ) or needed access to the raw metadata files of the vunnel workspaces. This will allow for anything that has access to the grypedb archive to have more fine-grained details with per-provider dates and no horrible hacks around the grypedb build date
The text was updated successfully, but these errors were encountered: