Repository navigation
chore(security): replace .trivyignore with VEX statements - #361
dannysauer wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #361 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 12 12
Lines 1518 1518
Branches 190 190
=========================================
Hits 1518 1518
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
🐳 Docker image built and pushed: |
7e02455 to
a18fa7a
Compare
Delete .trivyignore and the trivyignores inputs that pointed Trivy at it. A scan with both entries removed found nothing: Debian packages had no HIGH or CRITICAL findings, and jaraco.context is no longer in the image because the Dockerfile removes setuptools, which vendored it. Record GHSA-58pv-8j8x-9vj2 as not_affected with component_not_present. CVE-2026-0861 keeps its under_investigation statement. Update docs/vex.md and AGENTS.md: findings belong in .openvex.json, and an affected finding with no fix should keep the scan red for a maintainer to decide. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jc6x3m2t8YBrhUh7we64vu
a18fa7a to
d88892d
Compare
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🐳 Docker image built and pushed: |
|
🐳 Docker image built and pushed: |
Summary
.trivyignoreheld two entries, and neither still applies. The first push on this branch emptied the file, andSecurity Scan (PR)scanned the image without it:memalignoverflow) no longer appears. The image runsapt-get upgradeon every build, so a Debian fix would already be installed. I couldn't confirm the fix on Debian's security tracker from my session.jaraco.contextisn't in the image. GHSA-58pv-8j8x-9vj2 came in through the copy that setuptools vendors. The Dockerfile now removes setuptools and fails the build if it can still be imported.This PR:
.trivyignoreand the threetrivyignores:inputs inci.yml..openvex.jsonasnot_affectedwithcomponent_not_present, and explains why in the impact statement.under_investigationstatement in place until someone confirms the Debian fix.docs/vex.mdandAGENTS.md: findings are recorded only in.openvex.json. An affected finding with no fix keeps failingSecurity Scan (PR)until a maintainer decides what to do, instead of being silenced.Change type
feat: new behaviorfix: bug fixdocs: documentationrefactor: code structuretest: testschore: maintenanceImpact
stampbot.tomlbehavior is unchanged or documentedChecks
Security Scan (PR)with.trivyignoreemptied: passed. Debian packages and every Python package scanned clean, andjaraco.contextisn't in the package list.make test: 476 passed.SKIP=actionlint,helmlint,helm-kubeconform pre-commit run --all-files: passed. actionlint isn't installed in my session, so the workflow edit, which deletes three lines, relies on CI's lint.Related issues
Follows #360.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Jc6x3m2t8YBrhUh7we64vu