Open Source Tools
Submit a tool
Maintain or rely on a security tool with public source code? Propose it for the catalogue. Listing is free and editorial: sponsorship never buys a place or a better description.
We list
- Defensive and offensive security tools with public source code: scanners, SAST, SIEM, DFIR, fuzzers, smart-contract analysers and more.
- OSI-approved licences. Source-available licences (BUSL, Elastic, SSPL, PolyForm…) are accepted and clearly labelled "source-available".
- Projects that are maintained: a release or commits in the last 12 months, a README that explains usage.
- Dual-use tools (C2 frameworks, credential tools) with a legitimate testing purpose. They are labelled dual-use and carry no ads.
We don't list
- Malware, stealers, ransomware, RATs, botnets, or anything designed to attack people who did not consent.
- Closed-source products and SaaS. Vendors can request an Open Source Tools sponsorship or News & CVE advertising instead (pricing on request).
- Forks without meaningful changes, empty or placeholder repositories, abandoned projects, wrappers around a single API call.
- Submissions with misleading licences, stars bought or inflated, or marketing copy instead of facts.
Two ways to get listed
Free submissionFree
Your tool joins the review queue. Every submission is read by an editor, in order. The queue can be long: it may take several weeks before your tool is reviewed and published.
Same listing, same description rules, same ranking as every other tool.
Skip the queue + Featured listingPricing on request
A paid option for projects that need a date: review within a few working days, then a weekly Featured placement (pinned at the top of lists, labelled Featured and Sponsored). Review rules do not change: paying never buys acceptance, a description or a licence label.
What happens next
1. Sign in and choose
One email link, no password. In your dashboard, choose "List my open-source tool" (free) or "Skip the queue + Featured" (pricing on request).
2. Paste the repository
We read the public GitHub metadata (stars, licence, last push) and check the catalogue for duplicates.
3. Human review
An editor checks the licence, the code and the description. Most decisions take a few days.
4. Published
Accepted tools are scheduled and go live with the next catalogue update. You follow each step in My tools.
We may shorten or rewrite the description so every listing reads the same way. If a submission is not accepted you get the reason and can edit and resubmit. Questions: contact.