🔍 Add Vens plugin to Trivy plugin index #20
Merged
knqyf263 merged 2 commits intoaquasecurity:mainfrom Jan 21, 2026
Merged
Conversation
Contributor
Author
|
@knqyf263 PTAL |
Collaborator
|
Could you sign our CLA? |
Contributor
Author
done :) |
Collaborator
|
Thanks |
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.
Hi everyone,
https://github.com/venslabs/vens
This PR adds the Vens plugin from VensLabs to the official Trivy plugin registry.
What is Vens?
Vens is an AI-powered vulnerability prioritizer that transforms massive Trivy security reports into precise, actionable CycloneDX VEX documents using LLMs. It helps security teams focus on the risks that actually matter by adding business context to vulnerability assessments.
Vision & Impact: 🌐
Vens is pioneering the use of LLMs for vulnerability management in the open-source ecosystem. We're not just using CycloneDX – we're actively shaping it by contributing to the specification to better support risk-based prioritization (CycloneDX PR #722). 🚀
Example use case:
Imagine Trivy finds 500 vulnerabilities in your application. Instead of manually reviewing all of them:
trivy.jsonwith 500 CVEsconfig.yaml(e.g., your payment API has high impact: 9, high likelihood: 7)vens generatewith your SBOM and Trivy resultsResult: Focus on the 10 critical vulnerabilities in your payment API first, instead of wasting time on low-risk issues in unused dependencies.