Skip to content

fix(compose): surface per-service scan failures in user-facing summary - #160

Open
myukitty wants to merge 1 commit into
OWASP:mainfrom
myukitty:fix/surface-compose-scan-failures
Open

fix(compose): surface per-service scan failures in user-facing summary#160
myukitty wants to merge 1 commit into
OWASP:mainfrom
myukitty:fix/surface-compose-scan-failures

Conversation

@myukitty

@myukitty myukitty commented Aug 15, 2026

Copy link
Copy Markdown

When running Docker Compose scans, individual service failures (such as missing build context, image pull failures, or scanner runtime errors) were logged but not surfaced in the user-facing CLI quick-take summary block.

This PR:

  1. Tracks failed services and reasons in ComposeOrchestrator.run_full_scan() as structured entries in failed_services alongside total_services.
  2. Adds a summary line in _quick_take_lines() reporting N of M services had scan failures: <services> or direct compose-level error messages.
  3. Adds comprehensive unit and integration tests in tests/test_compose_scanner.py.

Fixes #131.

@github-actions github-actions Bot added cli Changes to the CLI entry point core Changes to core scanning logic tests Changes to the test suite labels Aug 15, 2026
Fixes OWASP#131. Track failed services and their error reasons during ComposeOrchestrator.run_full_scan and include a failed-services summary line in the CLI quick take block.
@myukitty
myukitty force-pushed the fix/surface-compose-scan-failures branch from f76a1d8 to 04f8171 Compare August 17, 2026 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cli Changes to the CLI entry point core Changes to core scanning logic tests Changes to the test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[GOOD FIRST ISSUE] Surface per-service compose scan failures in user-facing output

1 participant