Conversation
This branch has not been 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.
Summary
Fixes #197.
CycloneDX SBOM generation was producing the component inventory but not including vulnerability findings.
generate_sbom()now explicitly enables Trivy's vulnerability scanner using--scanners vuln, so vulnerability findings are included in the generated CycloneDX SBOM.Verification
Reproduced using:
ubuntu:stonking-20260705Before the fix:
After the fix:
The SBOM vulnerability count is higher because the normal DockSec report is severity-filtered, while the SBOM vulnerability scan is not.
Tests
Added regression coverage for:
Full test suite:
546 passed, 3 skipped, 153 subtests passed