Fazmin / cve-intel

CVE Intel 
 Know which vulnerabilities matter, and what to do about them. 
 A private desktop app for vulnerability triage, written in native Rust, with a CLI, REST API and MCP server for developers and AI agents. 
 36 tools, 38 data sources, on-device AI.
 What it is ·
 Getting started ·
 Features ·
 Install ·
 Local AI ·
 Data sources ·
 Developer notes ·
 Citing 
 Screenshots are taken on a 2560×1440 screen. Click one to see it full size. 
## What is CVE Intel?
Thousands of software vulnerabilities are published every year, each with an
ID such as CVE-2024-3400. For every one of them, security, IT and
development teams face the same question: *does this affect us, and do we
fix it now or can it wait?* Answering it usually means checking NVD, CISA,
FIRST, GitHub and vendor advisories by hand, one browser tab at a time.
CVE Intel does that legwork for you. Give it a vulnerability ID, your
project's dependency list, or a suspicious IP address, file hash or domain.
It checks up to 38 public security sources at once and comes back with one
clear, evidence-backed answer: what it is, how risky it is, whether
attackers are already using it, and what to do next. It also shows what
changed this week across those sources, and can watch the vendors, products
and packages you run.
It runs on your own computer as a desktop app. There is no CVE Intel account
or server: lookups go straight from your machine to the public sources, and
the built-in AI assistant runs locally unless you choose a cloud provider.
The same program also works from the command line, as a REST API, and as an
MCP server for AI agents (see Developer notes). It is
built for security analysts, IT and operations teams, developers checking
their dependencies, and anyone learning vulnerability management.
### What it helps you do
- **Decide whether to patch now.** Enter a CVE ID and get a risk score from
 0 to 100, a plain recommendation and how urgent it is, with the evidence
 behind it.
- **Put a list of vulnerabilities in order.** Paste up to 10 CVE IDs from a
 scanner report and get the order to patch them in.
- **Check your project's dependencies.** Paste a lockfile or SBOM and see
 which packages have known vulnerabilities and which version fixes them.
- **See what affects the products you run.** List the known vulnerabilities
 for a product and version, such as Apache Tomcat 9.0.80, with actively
 exploited ones first.
- **See what changed this week.** Open **Landscape** for new CISA KEV
 entries, CVEs ENISA marks exploited that KEV does not list yet, rising
 EPSS scores, new Metasploit modules and PoCs, new critical CVEs, Project
 Zero's in-the-wild zero-days and the latest CISA advisories. CVEs that
 several sources agree on are listed first.
- **Watch the products you run.** Add a vendor, product, package or CVE to
 the local watchlist. Each refresh records what changed: new CVEs, KEV
 listings, EPSS jumps, new exploits, CVSS revisions and newly available
 fixes.
- **Keep an eye on