Repository navigation
Support OpenVEX and CycloneDX VEX in validate - #115
Merged
Merged
Conversation
Deploying gatecheck-website with
|
| Latest commit: |
aa5cd57
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f5b659a2.gatecheck-website.pages.dev |
| Branch Preview URL: | https://vex-support.gatecheck-website.pages.dev |
validate --vex, GATECHECK_VEX, and the config's vex.files read OpenVEX and CycloneDX VEX. Grype, CycloneDX, Trivy, and osv-scanner findings marked not exploitable are dropped after the deny list, so they skip the KEV, EPSS, and severity rules. Statements that name packages match by package URL, and the latest statement wins. Fixes #102
BacchusJackson
force-pushed
the
vex-support
branch
from
November 4, 2026 18:36
c62c81a to
aa5cd57
Compare
This branch was successfully 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.
validatecan now skip findings that a VEX document marks as not exploitable, so accepted risk can live in a standard file and not only in the config's allow lists.--vex FILE(repeatable),GATECHECK_VEX(comma-separated, used when the flag is absent), andvex.filesin the config.analysis.state).not_affectedandfixed; CycloneDXnot_affected,false_positive,resolved, andresolved_with_pedigree.relatedVulnerabilities, TrivyVendorIDs, OSV aliases, CycloneDX references). When a statement names packages (OpenVEX subcomponents, CycloneDXaffects), the finding's package URL has to match. osv-scanner purls are built from the ecosystem. The latest statement wins.cveLimitdeny list. An explicit deny still fails, and skipped findings don't count toward the KEV, EPSS, or severity limits. Bundles pick it up as well.docs/vex.md.Tests cover the
pkg/vexparsers and matching (including a purl bug with scoped npm names), plus end-to-end validation on the sample Grype, Trivy, osv-scanner, and bundle reports. I also ran the built binary ontest/trivy-report.json: it went from exit 1 to exit 0 with--vex.Fixes #102
🤖 Generated with Claude Code