head to head · open source
ProjectDiscovery vs cve
ProjectDiscovery has 32,701 GitHub stars, 3,981 forks, 107 open issues and last shipped yesterday. cve has 8,197 stars, 981 forks, 21 open issues and last shipped 25 days ago. ProjectDiscovery leads on adoption by 299% (32,701 vs 8,197 stars). ProjectDiscovery is written in Go under MIT; cve is written in HTML under MIT. ProjectDiscovery has attracted 12% as many forks as stars, cve 12%. 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 | cve | |
|---|---|---|
| GitHub stars | ★ 33K | ★ 8.2K |
| License | MIT | MIT |
| Written in | Go | HTML |
| Last push | 2026-11-09 | 2026-10-16 |
| Forks | ⑂ 4.0K | ⑂ 981 |
| 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 cve if
- You want the cve feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches HTML
- You evaluated both and cve 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 cve
CVE PoC Almost every publicly available CVE PoC. Current hottest CVEs To see the complete history go here How it works Trickest Workflow Architecture TB; DZ (Too big; didn't zoom): Collect CVE details from cvelist (Shout out to CVE Project!) Split CVEs up by year. Find PoCs for each CVE using 2 techniques: 1. References Gather each CVE's References . Check if any of them points to a PoC using ffuf and a list of keywords Regex: (Thanks @joohoi!) Note : ffuf is awesome for more purposes than just content discovery. Get CVE referenced in HackerOne Reports AllVideoPocsFromHackerOne (Thanks @zeroc00I!) 2. Github…
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 cve more popular?
ProjectDiscovery has 32,701 GitHub stars and cve has 8,197. ProjectDiscovery has the larger community by that measure.
Are ProjectDiscovery and cve free?
Both are open source. ProjectDiscovery is licensed under MIT and cve under MIT. Neither carries a licence fee.
What is the difference between ProjectDiscovery and cve?
ProjectDiscovery is written in Go and cve in HTML. 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 cve?
Choose ProjectDiscovery if you want the larger community (32,701 stars) or its MIT licence terms. Choose cve if its feature set, stack or MIT licence fits better. Both are self-hostable.