Summary
Reporting and writing to a file only occurs if the full test suite is executed or if image scanning happens
Problem Statement
Reporting should be available when only AI analysis occurs with the CLI tool
Proposed Solution
The reporting functions internal to the DockerSecurityScanner should be removed and made globally available. This would allow reports to be generated with AI results only, not just an aggregation of AI and Scan results
Example Usage:
# How would this feature be used?
docksec Dockerfile --ai-only
Alternatives Considered
Any alternative approaches you've thought about.
Use Case
Who would benefit from this feature?
Acceptance Criteria
What does done look like?
Implementation Ideas
Reporting is removed from the parent class and added as its own standalone function
# Pseudo-code or high-level ideas
Related Issues
Summary
Reporting and writing to a file only occurs if the full test suite is executed or if image scanning happens
Problem Statement
Reporting should be available when only AI analysis occurs with the CLI tool
Proposed Solution
The reporting functions internal to the DockerSecurityScanner should be removed and made globally available. This would allow reports to be generated with AI results only, not just an aggregation of AI and Scan results
Example Usage:
# How would this feature be used? docksec Dockerfile --ai-onlyAlternatives Considered
Any alternative approaches you've thought about.
Use Case
Who would benefit from this feature?
Acceptance Criteria
What does done look like?
Implementation Ideas
Reporting is removed from the parent class and added as its own standalone function
# Pseudo-code or high-level ideasRelated Issues