The NVD is the U.S. government repository of standards-based vulnerability management data.
Search CVEs by keyword, product (CPE name), CVE ID, or date range. Get CVSS scores,
affected versions, references, and severity ratings. No API key required (optional for higher rate limits).
Quick Start
1. Install
See Install above.
2. Verify Setup
nvd-pp-cli doctor
This checks your configuration.
3. Try Your First Command
nvd-pp-cli json search-cpes
Usage
Run nvd-pp-cli --help for the full command reference and flag list.
Commands
json
Manage json
nvd-pp-cli json search-cpes - Search Common Platform Enumeration names to find exact product identifiers for vulnerability lookups.
nvd-pp-cli json search-cves - Search vulnerabilities by keyword, CVE ID, CPE name, publication date, or CVSS severity.
Output Formats
# Human-readable table (default in terminal, JSON when piped)
nvd-pp-cli json search-cpes
# JSON for scripting and agents
nvd-pp-cli json search-cpes --json
# Filter to specific fields
nvd-pp-cli json search-cpes --json --select id,name,status
# Dry run — show the request without sending
nvd-pp-cli json search-cpes --dry-run
# Agent mode — JSON + compact + no prompts in one flag
nvd-pp-cli json search-cpes --agent
Agent Usage
This CLI is designed for AI agent consumption:
- Non-interactive - never prompts, every input is a flag
- Pipeable -
--json output to stdout, errors to stderr
- Filterable -
--select id,name returns only fields you need
- Previewable -
--dry-run shows the request without sending
- Read-only by default - this CLI does not create, update, delete, publish, send, or mutate remote resources
- Offline-friendly - sync/search commands can use the local SQLite store when available
- Agent-safe by default - no colors or formatting unless
--human-friendly is set
Exit codes: 0 success, 2 usage error, 3 not found, 5 API error, 7 rate limited, 10 config error.
Health Check
nvd-pp-cli doctor
Verifies configuration and connectivity to the API.
Configuration
Config file: ~/.config/nvd-national-vulnerability-pp-cli/config.toml
Troubleshooting
Not found errors (exit code 3)
- Check the resource ID is correct
- Run the
list command to see available items
Generated by CLI Printing Press