Make it possible to download a differential update to the DB #143
Labels
enhancement
New feature or request
Comments
|
this kind of feature can be helpful (know when a record was updated) |
willmurphyscode
pushed a commit
that referenced
this issue
Mar 27, 2024
Bumps [pre-commit](https://github.com/pre-commit/pre-commit) from 3.2.1 to 3.2.2. - [Release notes](https://github.com/pre-commit/pre-commit/releases) - [Changelog](https://github.com/pre-commit/pre-commit/blob/main/CHANGELOG.md) - [Commits](pre-commit/pre-commit@v3.2.1...v3.2.2) --- updated-dependencies: - dependency-name: pre-commit dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
When
grypedecides to update the vulnerability database before a run,grypeshould be able to download a diff of what changed, rather than the entire database.Why is this needed:
Right now, when running
grypefor the first time that day, ~130MB download is needed for the new Grype DB. However, it is very likely that most of this data was downloaded the day before, with only a small number of additions and subtractions. It would be great if only this tiny diff could be downloaded each day, instead of the entire database.The text was updated successfully, but these errors were encountered: