fix(security): classify Dockerfile findings and require final-image ClamAV #57
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/workflows!57
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/source-dockerfile-findings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The manual base-images build in run #14 stops in source scanning because Trivy reports a Dockerfile absence finding without StartLine. This change gives source Dockerfile/general findings a stable target-scoped identity. HIGH findings remain blocking; unrelated line-less IaC still fails closed.
For the final exported container, publication now requires a fresh completed ClamAV scan. Signature-update or image-scan errors fail the publication gate and retain the scan evidence. Generic security scans keep their existing ClamAV warning behavior.
Validation: 47 focused scanner and publication tests passed locally. The broader suite has unrelated Windows-specific failures and is running in Linux CI. Tracks #56.
fix(security): retain line-less source Dockerfile findingsto fix(security): classify Dockerfile findings and require final-image ClamAVNot doing this
kiyi referenced this pull request2026-10-19 15:47:46 -05:00
Pull request closed