Repository navigation
ci: update OSV-Scanner to v2.7.0 - #1004
Merged
Merged
Conversation
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
![peco-review-bot[bot]](https://avatars.githubusercontent.com/in/3801177?s=60&v=4){kind=small}
There was a problem hiding this comment.
Verdict: 1 Low
Looks good — a clean, mechanical OSV-Scanner v2.3.8 → v2.7.0 bump (comment strings + download URL); the scan invocation, JSON parsing, suppression entries, and severity gates are all unchanged. One low concern: the version-specific capability claims about per-package/intersection CVE scoping were find-replaced to v2.7.0 without re-verification, and may now be stale (worth confirming against the v2.7.0 config docs). Note: WebSearch/WebFetch were unavailable here, so I could not independently verify the v2.7.0 release asset name or the scanner's current config feature set.
This branch was previously deployed
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 type of PR is this?
Description
Update the security scan to OSV-Scanner v2.7.0 and refresh version-specific comments. Suppression rules and severity thresholds are unchanged.
How is this tested?
Validation: workflow YAML, shell syntax, and whitespace checks passed; the existing JSON parser accepted v2.7.0 output. Old/new scans returned the same findings on identical inputs.