Exclude tests/ from Bandit scanning - #33
Open
jthDEV wants to merge 1 commit into
Open
Conversation
assert is pytest's normal assertion mechanism, not a stripped-in-
production security check — Bandit's B101 ("assert_used") flags every
occurrence regardless of context, which just produces noise for the
whole tests/ directory in GitHub Advanced Security.
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
1 participant
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.
Summary
assertintests/(e.g.tests/test_nuget.py, and now also the newtests/test_swift.py/tests/test_cocoapods.py)assertis stripped when Python runs with-O— a real concern for security checks in production code, butassertintests/is just pytest's normal assertion mechanism and never runs under-Oexcluded_paths: teststo.github/workflows/bandit.ymlso the scan stops flagging test files, keeping the signal for actual production codeTest plan
excluded_pathsinput confirmed via the action's own inline documentation comments in the workflow file