head to head · open source
ProjectDiscovery vs bundler-audit
ProjectDiscovery has 32,576 GitHub stars, 3,966 forks, 107 open issues and last shipped yesterday. bundler-audit has 2,764 stars, 245 forks, 49 open issues and last shipped 3 days ago. ProjectDiscovery leads on adoption by 1,079% (32,576 vs 2,764 stars). ProjectDiscovery is written in Go under MIT; bundler-audit is written in Ruby under GPL-3.0. ProjectDiscovery has attracted 12% as many forks as stars, bundler-audit 9%. ProjectDiscovery was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (security), 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
| ProjectDiscovery | bundler-audit | |
|---|---|---|
| GitHub stars | ★ 33K | ★ 2.8K |
| License | MIT | GPL-3.0 |
| Written in | Go | Ruby |
| Last push | 2026-11-04 | 2026-11-02 |
| Forks | ⑂ 4.0K | ⑂ 245 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick ProjectDiscovery if
- You weight community size — 33K stars and counting
- You want the MIT 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 ProjectDiscovery
English • 中文 • Korean • Indonesia • Spanish • 日本語 • Portuguese • Türkçe Nuclei is a modern, high performance vulnerability scanner that leverages simple YAML based templates. It empowers you to design custom vulnerability detection scenarios that mimic real world conditions, leading to zero false positives. Simple YAML format for creating and customizing vulnerability templates. Contributed by thousands of security professionals to tackle trending vulnerabilities. Reduce false positives by simulating real world steps to verify a vulnerability. Ultra fast parallel scan processing and request clustering. Integrate…
read the full ProjectDiscovery 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 ProjectDiscovery or bundler-audit more popular?
ProjectDiscovery has 32,576 GitHub stars and bundler-audit has 2,764. ProjectDiscovery has the larger community by that measure.
Are ProjectDiscovery and bundler-audit free?
Both are open source. ProjectDiscovery is licensed under MIT and bundler-audit under GPL-3.0. Neither carries a licence fee.
What is the difference between ProjectDiscovery and bundler-audit?
ProjectDiscovery 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, ProjectDiscovery or bundler-audit?
Choose ProjectDiscovery if you want the larger community (32,576 stars) or its MIT licence terms. Choose bundler-audit if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.