head to head · open source

Osintgram vs cve

Osintgram has 15,485 GitHub stars, 3,262 forks, 1 open issues and last shipped 10 days ago. cve has 8,192 stars, 982 forks, 21 open issues and last shipped 24 days ago. Osintgram leads on adoption by 89% (15,485 vs 8,192 stars). Osintgram is written in Python under GPL-3.0; cve is written in HTML under MIT. Osintgram has attracted 21% as many forks as stars, cve 12%. Osintgram was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (hacking, penetration-testing), 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.

Osintgram ★ 15K cve ★ 8.2K category Security & Privacy

← all 20902 open source comparisons

Side by side

Osintgram cve
GitHub stars ★ 15K ★ 8.2K
License GPL-3.0 MIT
Written in Python HTML
Last push 2026-10-30 2026-10-16
Forks ⑂ 3.3K ⑂ 982
Self-hosting Yes Yes
Data ownership Your server Your server

pick Osintgram if

  • You weight community size — 15K stars and counting
  • You want the GPL-3.0 license terms
  • Your stack matches Python
  • You value the larger contributor base for long-term maintenance

full Osintgram profile →

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

full cve profile →

About Osintgram

Osintgram 🔎📸 Point it at an Instagram account and find out who's behind it. Osintgram collects, cross references and lays out everything a public profile gives away — followers, captions, hashtags, geotagged locations, posting habits, public contact details — in a web interface you run on your own machine. Ask in plain language and a local AI model figures out which lookups to run. Or don't: pick the commands yourself and skip the model entirely. Why you might like it It answers questions, not just commands. "How many followers do they have and which hashtags do they use most?" runs three lookups and comes…

read the full Osintgram 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…

read the full cve 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 Osintgram or cve more popular?

Osintgram has 15,485 GitHub stars and cve has 8,192. Osintgram has the larger community by that measure.

Are Osintgram and cve free?

Both are open source. Osintgram is licensed under GPL-3.0 and cve under MIT. Neither carries a licence fee.

What is the difference between Osintgram and cve?

Osintgram is written in Python 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, Osintgram or cve?

Choose Osintgram if you want the larger community (15,485 stars) or its GPL-3.0 licence terms. Choose cve if its feature set, stack or MIT licence fits better. Both are self-hostable.