Improve progress bar accuracy

[jkondrat]

When scanning Docker images, the progress bar currently shows "Finalizing Report" for too much of the process, which makes the scan status unclear.

Please improve the progress bar so it reflects the actual scan progress more accurately. It would also be helpful to show more details during the scan, for example which image is currently being scanned.

[ClydeTN]

Hi @igor-soldev

I'd like to look into this one, and I wanted to share what I found before proposing a fix.

The progress bar in the web UI (startScanProgress() in static/app.js) is currently driven by a setInterval timer. It just creeps a number toward 98% and lights up the steps (Clone → Init → IaC → Containers → Report) when that fake number crosses hardcoded thresholds (15/30/60/85/95%). It isn't tied to the actual scan. On the backend, /api/scan/github runs the whole scan synchronously and returns the final result in one response, so the frontend has no real progress to show.

That's why the accuracy is off:

• fast scans barely move, then jump to 100%;
• long scans pin at 98% and look frozen;
• the "Container vulnerability scan" step still lights up even when containers aren't being scanned;
• a failed scan keeps creeping as if everything's fine.

What I'd propose is wiring the bar to real progress: have scan_directory() emit stage events through a callback, stream them from the backend (Server-Sent Events, or a polled status endpoint if you'd prefer), and drive the bar and steps from those real events, keeping the current animation as a fallback. The main thing to flag is that this changes the scan request from a single blocking call into a streamed one.

Before I start, does that direction sound good to you, and do you have a preference between SSE and a polled status endpoint? I'd rather align on the approach than guess. Happy to keep it to a single, focused PR with manual testing.

[igor-soldev]

Hi @ClydeTN,

thanks for the analysis - your assessment matches my understanding of the issue.

I agree that the current progress bar should be driven by actual scan progress rather than a timer. Showing the current scan stage (and, where possible, which image is being scanned) would also be a useful improvement.

I'm open to either SSE or polling. Please choose the option that keeps the implementation simplest and easiest to maintain. The main goal is to make the progress indicator reflect the real scan state and handle optional/failed scan stages correctly.

Feel free to open a draft PR if you'd like feedback on the implementation before it's finished.

Also, @jkondrat, if you have any preferences or additional expectations for this issue, please feel free to share them as well.