Fix #403: exit with error when --gemfile-lock is not a valid lock file#414
Open
kallal79 wants to merge 2 commits into
Open
Fix #403: exit with error when --gemfile-lock is not a valid lock file#414kallal79 wants to merge 2 commits into
kallal79 wants to merge 2 commits into
Conversation
…ock file Bundler::LockfileParser silently accepts any file (Gemfile, README.md, etc.) and returns empty results, causing bundle-audit to exit 0 with 'No vulnerabilities found' even when given the wrong file. Changes: - Add Scanner::InvalidGemfileLock exception class - Add LOCKFILE_HEADER_RE regexp to validate lock file content before parsing - Raise InvalidGemfileLock in Scanner#initialize when file does not start with a recognised Bundler lockfile section header - Rescue InvalidGemfileLock in CLI#check and exit with status 1 plus a descriptive stderr message - Add spec for Scanner#initialize raising InvalidGemfileLock - Add specs for CLI#check printing error to stderr and exiting with 1 Fixes rubysec#403
simi
approved these changes
May 31, 2026
Contributor
Author
|
Thanks @simi for the approval — I’ll resolve the merge conflicts in spec/scanner_spec.rb and update the branch so it’s ready for review by @flavorjones and @jasnow. |
Contributor
|
@kallal79 I'm happy to rebase also or help, just ping me. |
Member
|
Please fix "MERGE CONFLICTS". |
kallal79
force-pushed
the
fix/issue-403-invalid-gemfile-lock
branch
from
b3e3205 to
edfe07d
Compare
jasnow
approved these changes
Jun 2, 2026
Member
jasnow
left a comment
jasnow
left a comment
There was a problem hiding this comment.
I do not see anything to comment on.
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.
Bundler::LockfileParser silently accepts any file (Gemfile, README.md, etc.) and returns empty results, causing bundle-audit to exit 0 with 'No vulnerabilities found' even when given the wrong file.
Changes:
Fixes #403