fix: keep Bandit coverage aligned with discovered files - #695
Open
ApexWorm wants to merge 3 commits into
Open
Conversation
Author
|
GPT 5.6 Terra Ultra apparently identified this issue while working and then decided to fix it and then make a PR here without my approval at any stage, cool |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A recursive root Bandit invocation can time out after traversing files outside Desloppify source discovery. That leaves Python security coverage reduced even when the configured source scope is fast to scan.
Fix
Run Bandit over deduplicated, discovered Python file batches; preserve a single total timeout; retain successful partial findings while reporting reduced coverage for timeouts, fatal exits, JSON errors, empty output, and missing target metrics. Legacy direct recursive callers remain supported.
Verification