Security tooling you can use for free and read line by line.

The Community tier is rate-limited and has no time limit or card. The tools are open source, the data comes in formats other tools already read, and every record links to its original source, including the records we publish ourselves.

Get a free API key brew install vulnetix/tap/vulnetix

Live right now, with no account needed: KEV Watch, Bug Bounty Intelligence, the Red Hat archive, the intelligence sources and the Rules Registry.

Per-seat pricing, three-year contracts, and the blame lands on you. Not with Vulnetix, not even on the Community tier.

Most security vendors charge per seat, ask for multi-year enterprise contracts, and cover little more than the CVE Program and NVD, whose enrichment has fallen behind since February 2024. When a detection is wrong or a fix they handed you does not land, the support ticket comes back saying you configured it badly.

A typical proprietary vendorVulnetix, Community tier
PricePer seat, on a multi-year enterprise contractFree, with no contract and no card
CoverageThe CVE Program and NVD, plus a feed you cannot inspect160 named sources, with our own advisories public on GitHub
Record qualityInherits whatever NVD has not enriched yetReconciled across sources, each one cited
Detection logicClosed rules you cannot readRego you can read, fork and test
A wrong findingClosed as a configuration issue on your sideOur defect, and we fix the record
LeavingA proprietary export, if anyOpen formats your next tool already reads

Never accept exorbitant prices or user blame again. The Community tier shows what good looks like, and any vendor still charging per seat for CVE-only coverage will have to explain why.

Read why CVE and NVD coverage alone falls short

The tools that touch your code are open source.

The scanner, the coding harness and the agent plugin are published under OSI-approved licences. You can fork them, audit them and run them without a Vulnetix account.

The OSI logo marks licences approved by the Open Source Initiative. It is a trademark of the Open Source Initiative.

Every record links to where it came from, including the ones we write.

We reconcile 160 named upstream sources and keep the upstream ID on every record. When Vulnetix finds a vulnerability nobody has published, we issue it as GCVE GNA 110 and commit it to a public GitHub repository, so you can clone the original source of our own records too.

160 sources, all named

The full list is public, and every record keeps its upstream identifiers so you can check our work against the original. See the sources

New records go to GitHub

As GCVE GNA 110 we publish in CVE JSON 5, OSV and Vulnetix formats under CC-BY-4.0. You can clone, mirror and cite the repository. Open the repository

Specs written in public

CRIT, our format for cloud vulnerability records, is an IETF draft. We donated our Transparency Exchange server to OWASP. Read the CRIT draft

Your source code stays on your machine.

Scanning runs locally. The only thing that crosses the network is a package name and version or an identifier, and you decide whether that leaves too.

Leave whenever you like, with all of your data.

Every export is an open standard that the tools you already run can read. Moving to another product means pointing it at the same files.

Twelve vendor archives, ranked the way you choose.

Every month of every vendor's advisories with EPSS, KEV and proof-of-concept data, an end-of-life calendar, and four ways to order the list: Vulnetix priority, vendor rating, CVSS or EPSS. Browse the archives

What the Community tier includes

Start on the free tier and stay as long as you like.

Paid plans add enrichment, defence rules and more keys to the same responses you already use.

Get a free API key Compare plans