Skip to content

Regarding the future of ruby-advisory-db repo #1040

@jasnow

Description

@jasnow

Regarding the future of ruby-advisory-db repo

On May 5, 2026, posted this to the rubyonrails-link.slack.com and bundler.slack.com web sites:

Ruby Community,

I want to thank the RubySec team members @postmodern and @reedloden for 13 years of 
tooling and support to the Ruby and Ruby Gems community.

As a RubySec/ruby-advisory (read-only) team member (@jasnow), I can
concur what @rakvium said in his [Comment](https://github.com/rubysec/ruby-advisory-db/pull/1027#issuecomment-4370748262) .

 * It appears that the RubySec/"bundle audit"-related repos (ruby-advisory-db, bundle-audit)] 
   have had no new, changed, or enhanced advisories to ruby-advisory-db database which is 
   used by bundle-audit (aka "bundle audit") since March 30, 2026.

In other words as Jeff Bigler (@jbigler) said:

The maintainers of the repo containing security warnings for ruby gems are out of contact, 
meaning "bundler audit" has no up-to-date warnings past March 30th.

THEREFORE I expect to track the status and changes to this repo here in this issue.
Please comment below to thanks the team, sponsor this project, or provide input.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions