PatchRadar
PatchRadar 🛡️
Know when your software is vulnerable — before attackers do.
PatchRadar monitors CVE feeds in realtime and alerts you when a new vulnerability affects your software stack. No more manually checking NVD, MSRC, or Snyk — just add your software and let PatchRadar watch for you.
✨ Features
- 🔍 Realtime CVE monitoring — scans NVD, MSRC and Debian Security Tracker for new vulnerabilities
- 📋 Personal watchlist — add any software you want to monitor
- 🎨 Beautiful web UI — dark theme dashboard with charts and filters
- 💻 CLI first — full command line interface for automation
- 📊 CVSS scoring — color-coded severity (Critical / High / Medium / Low)
- 🐧 Debian Security Tracker — monitors open CVEs for Debian/Ubuntu packages
- 💾 Local SQLite — all data stored locally, no cloud, no account needed
- 🐍 Python 3.11+ — modern async architecture with httpx and FastAPI
🚀 Installation
pip install patchradar
📖 Usage
CLI
# Add software to your watchlist
patchradar add proxmox
patchradar add bitwarden
patchradar add "windows 10"
# Show your watchlist
patchradar list
# Scan for CVEs (last 30 days)
patchradar scan --days 30
# Show latest CVEs in terminal
patchradar status
# Remove software
patchradar remove proxmox
Web UI
patchradar serve
# Open http://localhost:8000
NVD API key (optional)
NVD limits clients without an API key to 5 requests per 30 seconds; a key raises
it to 50. A long scan needs several requests per keyword — NVD refuses any date
range wider than 120 days, so --days 730 is split into seven windows — and a
watchlist of any size will reach the keyless limit. PatchRadar paces its requests
to stay under whichever limit applies, which makes a keyless scan slower rather
than incomplete.
export NVD_API_KEY=your-key # https://nvd.nist.gov/developers/request-an-api-key
patchradar scan --days 365
The key is sent as a request header, never in the URL. If a source fails for every entry in the watchlist, the scan says so after the total rather than leaving one warning per entry: a count of CVEs that came from one source out of two is not the same as a complete scan.
📡 Sources
| Source | Type | Status |
|---|---|---|
| NVD | CVE Database | ✅ Active |
| MSRC | Microsoft Patch Tuesday | ✅ Active |
| Debian Security | Linux packages | ✅ Active |
| CISA KEV | Known exploited vulnerabilities | ✅ Active |
KEV answers a different question from the others. They report what has been
published about a package; KEV reports what is being exploited right now,
with CISA's own remediation deadline. It carries no severity of its own and
PatchRadar does not invent one — the fact travels as known_exploited, which
is worth more than a score: on a sample of 695 CVEs matched against installed
software, sorting by CVSS put five 10.0 entries on top, none of them exploited,
while the four listed in KEV scored 9.8, 8.8, 8.6 and 7.8.
🗓️ Versioning
PatchRadar uses CalVer — YYYY.MM.PATCH.
⚡ Benchmarks
Performance is tracked continuously with CodSpeed. The benchmarks live in benchmarks/ and cover the CVE collectors, the SQLite layer, the API endpoints and the CLI table rendering.
pip install --group dev -e .
pytest benchmarks/ # correctness check, no measurement
codspeed run --mode simulation -- pytest benchmarks/ --codspeed
🤝 Contributing
Contributions are welcome! Feel free to open issues or pull requests.
📄 License
MIT — see LICENSE for details.
1 maintainer
Release files for patchradar 2026.41
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| patchradar-2026.41.tar.gz | 185.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| patchradar-2026.41-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 240.6 kB
Release files / patchradar-2026.41.tar.gz
| Download URL | patchradar-2026.41.tar.gz |
|---|---|
| Size | 185.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ead0ee1f8e74eaf660e42bd33f26ffb62096ba52b3f609c8d28c22c985a4f1b
|
|
BLAKE2b-256 checksum How to use checksums |
2c032fb7a7f4305920d6f170251fa250d5b8acef55d25c73164278aade2ec1f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency logRelease files / patchradar-2026.41-py3-none-any.whl
| Download URL | patchradar-2026.41-py3-none-any.whl |
|---|---|
| Size | 54.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c107cc475856837c2d536111c74ab971e2da97ab3a3e0fcebc755e168639e473
|
|
BLAKE2b-256 checksum How to use checksums |
6ea967dc6e76fc3f956034da5377467ac15547d065c9c581fcf4d7cb2044a02d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency log
