Check Gemfile.lock for vulnerable dependencies

Upload or paste your Gemfile.lock. We check every Ruby package version in it against OSV.dev and email you the vulnerable ones, the version that fixes them and the Bundler command to upgrade. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About Gemfile.lock

Gemfile.lock is written by Bundler next to Gemfile. It records the exact version of every gem, including the gems your gems depend on.

To write or refresh it:

bundle lock

bundle install also writes it. Commit it.

Good to know

  • Gemfile cannot be checked: it has version ranges.
  • Platform-specific gems (like nokogiri 1.16.0-x86_64-linux) are read as their plain version (1.16.0).

Fixing a vulnerable package

The report gives the fixed version for each vulnerable package (FIXED below). With Bundler:

# Upgrade one gem, changing as little else as possible
bundle update gem --conservative

For an indirect gem, bundle update with its name also works when its parents allow the fixed version; otherwise upgrade the parent gem.

Then run your tests and commit the updated Gemfile.lock.

bundle-audit (the bundler-audit gem) and this check

bundler-audit uses the Ruby Advisory Database, which OSV.dev includes. This check needs nothing installed and works for your other languages too.

Other lockfiles

Last updated .