Ecosystem · Ruby · Bundler
Vulnerabilities in your gems, and in your Ruby version.
LibWatch reads Gemfile and Gemfile.lock, checks every gem and tracks the end of life of your Ruby version. Rails or plain Ruby: the same analysis.
What LibWatch reads in the repository
GemfileGemfile.lock*.gemspec.ruby-version
Language version: .ruby-version or .tool-versions
Nothing else: no cloning, no code run.
What LibWatch checks
The gems, and the Ruby version
RubyGems packages
Known vulnerabilities
Every package in the lockfile checked against OSV, which includes GitHub advisories.
Ruby version
End of life
The declared version is tracked: you know when it stops getting fixes.
Health
License policy
Licenses that conflict with your project's policy are flagged.
An alert, in practice
A vulnerability in a gem, with the version that fixes it
The vulnerabilities that affect your versions, with the fixed version. Nothing more.
Real severity
CVSS severity and presence in the CISA KEV catalog
What to do
The fixed version, and the affected project
Where
Email, Slack, Zulip or webhook, set per project
back-office · Rails
Example · analysis from October 22
-
End of life
Ruby (declared)
3.2.4
-
Medium severity
rack
3.0.9
-
Up to date
rails
8.0.2
Rechecked every night at 2 a.m.
End of life
Where your Ruby version stands
Official ruby-lang.org schedule, checked on October 22, 2026.
| Version | Status | End of life | Action |
|---|---|---|---|
| Ruby 3.4 | Bug fixes | → March 2028 | Recommended version |
| Ruby 3.3 | Security only | → March 2027 | Plan the upgrade |
| Ruby 3.2 | End of life | Since March 2026 | Upgrade now |
Dates checked on October 22, 2026.
Get started
Your first report in a few minutes
No pipeline to change.
Connect GitHub or GitLab
Self-hosted GitLab instances included.
Choose your Ruby repositories
LibWatch finds the files listed above on its own, even in a monorepo.
Read the report, set up alerts
Exploited vulnerabilities first, fixed versions, language end of life.
Frequently asked questions
LibWatch and Ruby
Do I need to install anything in the project?
No. LibWatch reads dependency files through the GitHub or GitLab API, without adding anything to your pipeline.
Are private registries supported?
Yes. A package from a private registry is identified as such: its name is never sent to a third-party service, and it stays in the project's inventory.
Does LibWatch detect the version installed on the server?
No. LibWatch reads the version declared in the repository (version file, lockfile or manifest). It has no access to your servers.