head to head · open source
osv-scanner vs bundler-audit
osv-scanner has 11,387 GitHub stars, 834 forks, 113 open issues and last shipped yesterday. bundler-audit has 2,764 stars, 245 forks, 49 open issues and last shipped 3 days ago. osv-scanner leads on adoption by 312% (11,387 vs 2,764 stars). osv-scanner is written in Go under Apache-2.0; bundler-audit is written in Ruby under GPL-3.0. osv-scanner has attracted 7% as many forks as stars, bundler-audit 9%. osv-scanner was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (security-audit, security-tools), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| osv-scanner | bundler-audit | |
|---|---|---|
| GitHub stars | ★ 11K | ★ 2.8K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Go | Ruby |
| Last push | 2026-11-04 | 2026-11-02 |
| Forks | ⑂ 834 | ⑂ 245 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick osv-scanner if
- You weight community size — 11K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick bundler-audit if
- You want the bundler-audit feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Ruby
- You evaluated both and bundler-audit fits your workflow better
About osv-scanner
Use OSV Scanner to find existing vulnerabilities affecting your project's dependencies. OSV Scanner provides an officially supported frontend to the OSV database and CLI interface to OSV Scalibr that connects a project’s list of dependencies with the vulnerabilities that affect them. OSV Scanner supports a wide range of project types, package managers and features, including but not limited to: Languages: C/C++, Dart, Elixir, Go, Java, Javascript, PHP, Python, R, Ruby, Rust. Package Managers: npm, pip, yarn, maven, go modules, cargo, gem, composer, nuget and others. Operating Systems: Detects vulnerabilities in…
read the full osv-scanner overview →
About bundler-audit
bundler audit Homepage Issues Documentation Description Patch level verification for [bundler]. Features Checks for vulnerable versions of gems in Gemfile.lock . Checks for insecure gem sources ( and git:// ). Allows ignoring certain advisories that have been manually worked around. Prints advisory information. Does not require a network connection. Synopsis Audit a project's Gemfile.lock : Update the [ruby advisory db] that bundle audit uses: Update the [ruby advisory db] and check Gemfile.lock (useful for CI runs): Checking the Gemfile.lock without updating the [ruby advisory db]: Ignore specific advisories…
read the full bundler-audit overview →
More in Security & Privacy
Related comparisons
More Threat Detection & Response projects
Compare either of these against the rest of the Threat Detection & Response field.
Frequently asked questions
Is osv-scanner or bundler-audit more popular?
osv-scanner has 11,387 GitHub stars and bundler-audit has 2,764. osv-scanner has the larger community by that measure.
Are osv-scanner and bundler-audit free?
Both are open source. osv-scanner is licensed under Apache-2.0 and bundler-audit under GPL-3.0. Neither carries a licence fee.
What is the difference between osv-scanner and bundler-audit?
osv-scanner is written in Go and bundler-audit in Ruby. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, osv-scanner or bundler-audit?
Choose osv-scanner if you want the larger community (11,387 stars) or its Apache-2.0 licence terms. Choose bundler-audit if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.