chore(deps): bump vuls-data-update and vuls2 to latest#2602
Merged
Conversation
github.com/MaineK00n/vuls2 is already at the latest main (69ab575). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the vuls-data-update dependency to the latest upstream commit so Vuls benefits from recent extractor fixes in the data update pipeline.
Changes:
- Bump
github.com/MaineK00n/vuls-data-updatepseudo-version ingo.mod - Refresh
go.sumchecksums for the updatedvuls-data-updateversion
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| go.mod | Updates the required github.com/MaineK00n/vuls-data-update version to the newer pseudo-version. |
| go.sum | Updates module checksums to match the bumped vuls-data-update version. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Includes db fetch performance improvements: - perf(db/fetch): disable zstd lowMem to avoid window-sized memmoves (MaineK00n/vuls2#399) - fix(db/fetch): stream manifest directly instead of copying to memory store (MaineK00n/vuls2#401) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The previous pin 63b24be was the head of the main branch; the default (and most up-to-date) branch of vuls-data-update is nightly. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What did you implement:
Bump github.com/MaineK00n/vuls-data-update and github.com/MaineK00n/vuls2 to their latest upstream heads (vuls-data-update: nightly branch, vuls2: main branch).
Upstream changes (MaineK00n/vuls-data-update@f3c7f13ad814...b52d4dc1721c):
Upstream changes (MaineK00n/vuls2@69ab575c2ebe...49df52eeaa6c), notably vuls2 db fetch performance improvements:
Type of change
How Has This Been Tested?
go build ./...andgo test ./detector/...passvuls reportagainst a pseudo server withcpeNames = ["cpe:/a:openssl:openssl:1.0.2k"]starting from a deleted vuls2 db, on master and on this branch:vuls2 db fetch (nightly, ~11GB) is roughly 7x faster thanks to MaineK00n/vuls2#399 and MaineK00n/vuls2#401, at the cost of a modest memory increase. Detection results are identical (61 CVEs detected / 51 after confidence filter).
Checklist:
🤖 Generated with Claude Code