fix: report skipped oversized and unreadable files during scan - #31
Merged
royalpinto007 merged 3 commits intoSep 12, 2026
Merged
Conversation
Track files that exceed the 2 MB read limit or cannot be read, surface them in text/JSON reports and stderr warnings, and fail the run so padded payloads cannot look like a clean scan. Fixes AgentPostmortem#4 Co-authored-by: Sharad. <sharadvc@users.noreply.github.com>
1 task
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
Files over 2 MB (and unreadable files) were skipped silently, so padded payloads could evade the scanner without a word. The scan now surfaces clear skip reporting for oversized/unreadable files, with a regression test.
Test plan
npm testFixes #4