Skip to content

Allow passing multiple Gemfile.lock files to bundler audit#224

Open
fatkodima wants to merge 2 commits intorubysec:masterfrom
fatkodima:multiple-lockfiles
Open

Allow passing multiple Gemfile.lock files to bundler audit#224
fatkodima wants to merge 2 commits intorubysec:masterfrom
fatkodima:multiple-lockfiles

Conversation

@fatkodima
Copy link
Contributor

@fatkodima fatkodima commented Aug 29, 2019 •
edited
Loading 

# checks Gemfile.lock by default, as now
$ bundler audit

# checks multiple lockfiles
$ bundler audit check Gemfile.lock GemfileNext.lock

Replaces #212
Replaces #207
Replaces #200
Replaces #171

Closes #178
Closes #181

@postmodern postmodern changed the title Allow passing Gemfile.lock paths to bundler audit Allow passing multiple Gemfile.lock files to bundler audit Dec 17, 2020
@postmodern
Copy link
Member

postmodern commented Dec 17, 2020

Auditing multiple Gemfile.lock files in one run is an interesting idea. Not sure whether users with multiple Gemfile.lock files would prefer to audit them individually via some set of CI tasks, or in one run; with annotated output indicated which Gemfile.lock file contains the vulnerable gems?

@postmodern postmodern mentioned this pull request Dec 17, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

discussion feature

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Refactor Bundler::Audit::Scanner#initialize allow passing Gemfile.lock paths to bundle audit

2 participants

@fatkodima @postmodern