-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Audit ruby version, when specified #229
Comments
It would also be nice if something could audit rubygems which I know is not in the lock file. |
A few years back I wrote https://github.com/lucasluitjes/recent_ruby which does exactly that. I don't know if it meets the project standards for bundler-audit but I thought I'd mention it just in case it's helpful. |
@postmodern @reedloden Before I will invest some time into this feature, is this something that will be merged? |
@fatkodima I would be interested in something like this, not sure if @postmodern would agree. @lucasluitjes Does It would be useful to know that if you are using Ruby 2.7.x, then you have this known CVE to worry about: https://www.ruby-lang.org/en/news/2023/03/30/redos-in-time-cve-2023-28756/ |
@etagwerker No, Listing CVEs would be handy feature though. Not sure where to reliably pull that data from. I looked at https://github.com/rubysec/ruby-advisory-db/tree/master/rubies/ruby but it doesn't seem up to date (CVE-2023-28756 isn't in there, for example). If you know a good data source, feel free to make an issue on the https://github.com/lucasluitjes/recent_ruby repository. |
Apparently bundler 2.4 now requires that the Although, I'm still not 100% certain that the ruby version in the |
When Gemfile.lock includes ruby version, something like
than verify it for vulnerabilities.
If this is a valuable feature for this project, then I will send a PR.
The text was updated successfully, but these errors were encountered: