head to head · open source
vuls vs bundler-audit
vuls has 12,324 GitHub stars, 1,247 forks, 92 open issues and last shipped 4 days ago. bundler-audit has 2,764 stars, 245 forks, 49 open issues and last shipped 3 days ago. vuls leads on adoption by 346% (12,324 vs 2,764 stars). vuls is written in Go under GPL-3.0; bundler-audit is written in Ruby under GPL-3.0. vuls has attracted 10% as many forks as stars, bundler-audit 9%. bundler-audit was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (security, 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
| vuls | bundler-audit | |
|---|---|---|
| GitHub stars | ★ 12K | ★ 2.8K |
| License | GPL-3.0 | GPL-3.0 |
| Written in | Go | Ruby |
| Last push | 2026-11-01 | 2026-11-02 |
| Forks | ⑂ 1.2K | ⑂ 245 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick vuls if
- You weight community size — 12K stars and counting
- You want the GPL-3.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 vuls
Vuls: VULnerability Scanner Vulnerability scanner for Linux/FreeBSD, agent less, written in Go. Twitter: @vuls en Abstract For a system administrator, having to perform security vulnerability analysis and software update on a daily basis can be a burden. To avoid downtime in a production environment, it is common for a system administrator to choose not to use the automatic update option provided by the package manager and to perform update manually. This leads to the following problems. The system administrator will have to constantly watch out for any new vulnerabilities in NVD (National Vulnerability…
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 vuls or bundler-audit more popular?
vuls has 12,324 GitHub stars and bundler-audit has 2,764. vuls has the larger community by that measure.
Are vuls and bundler-audit free?
Both are open source. vuls is licensed under GPL-3.0 and bundler-audit under GPL-3.0. Neither carries a licence fee.
What is the difference between vuls and bundler-audit?
vuls 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, vuls or bundler-audit?
Choose vuls if you want the larger community (12,324 stars) or its GPL-3.0 licence terms. Choose bundler-audit if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.