Skip to content

[SAR] APPENG-5140: Add CVE scanning to CI pipeline#188

Open
yuvalk wants to merge 2 commits into
RHEcosystemAppEng:mainfrom
yuvalk:fix/APPENG-5140-ci-security-scanning
Open

[SAR] APPENG-5140: Add CVE scanning to CI pipeline#188
yuvalk wants to merge 2 commits into
RHEcosystemAppEng:mainfrom
yuvalk:fix/APPENG-5140-ci-security-scanning

Conversation

@yuvalk
Copy link
Copy Markdown
Collaborator

@yuvalk yuvalk commented May 6, 2026

Summary

Addresses APPENG-5140.

Add automated security scanning to the CI pipeline using pip-audit for Python dependency vulnerabilities and Trivy for container image CVE scanning.

Changes

  • Add scan job to .github/workflows/ci.yml that runs pip-audit and Trivy
  • Add pip-audit>=2.7.0 to dev dependencies in pyproject.toml
  • Update ci-gate job to include scan results in the gate check
  • Scan uses exit-code 0 (non-blocking) initially to establish baseline

SAR Reference

  • CWE: CWE-1395 (Dependency on Vulnerable Third-Party Component)
  • Impact: Medium

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

Add a security scanning job to the CI pipeline that runs pip-audit
for Python dependency vulnerabilities and Trivy for container image
CVE scanning. This provides automated supply chain security checks.

- Add 'scan' job to CI workflow with pip-audit and Trivy steps
- Add pip-audit to dev dependencies in pyproject.toml
- Gate CI on scan job results alongside lint, test, and build

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Comment thread .github/workflows/ci.yml Outdated

- name: Build image for scanning
run: |
docker build -t lightspeed-agent:scan -f Containerfile .
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use podman as in the other build in this file?

Aligns with the existing CI build step which uses podman.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@yuvalk
Copy link
Copy Markdown
Collaborator Author

yuvalk commented May 7, 2026

Fixed - changed docker build to podman build to match the existing CI build step.

Copy link
Copy Markdown
Collaborator

@luis5tb luis5tb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but it seems it cannot fine the image: unable to find the specified image "lightspeed-agent:scan"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants