fix: apply extension/shebang filter to single-file targets - #28
Merged
royalpinto007 merged 1 commit intoSep 12, 2026
Conversation
Apply the same scannable-file rules when the scan target is a file path as when walking a directory, so binary single-file targets are skipped. Fixes AgentPostmortem#11 Co-authored-by: Sharad. <sharadvc@users.noreply.github.com>
Contributor
Author
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
3 participants
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
collectFilespreviously added a single-file path unconditionally, so binaries could still be read as UTF-8. Directory walks already filtered by extension/shebang; this applies the same rules to the single-file branch.Test plan
npm test— includes regression forbinary-target.bin(expectfiles: 0, no findings)Fixes #11