ZeroDayDB CLI

FREE

Run the Python CLI from a ZeroDayDB checkout to scan dependency manifests against live vulnerability data.

Practical Manifest Scanning

Point the CLI at a project directory and it will inspect supported manifests, query ZeroDayDB, and return a report you can use locally or in automation.

Supported Manifest Detection

Covers npm, Python, Go, and Rust manifests used by the current scanner.

Threshold-Based Exits

Use --fail-on to gate CI on severity.

Readable or JSON Output

Choose Rich tables for humans or --json for scripts.

Watch Mode

Repeat scans on a polling interval while you work.

Free to Use

The CLI is included at no extra cost. Today the supported path is the Python workspace command shown below, not a published npm or Homebrew package.

Why that matters: the commands on this page are meant to be run as-is. We would rather show the real entrypoint than a friendlier install story that does not exist yet.

Quick Scan

Scan the current directory for supported manifests.

uv run --project apps/cli zerodaydb scan .

Scan a Specific Directory

Point the CLI at any project directory instead of scanning your current working tree.

uv run --project apps/cli zerodaydb scan /path/to/project

Thresholds and Output

Use the flags the current scanner actually supports to tune exits and output formatting.

uv run --project apps/cli zerodaydb scan . --fail-on high # Fail when high-or-worse findings are present

uv run --project apps/cli zerodaydb scan . --json # Emit machine-readable output

uv run --project apps/cli zerodaydb scan . --api-key $ZERODAYDB_API_KEY # Override the stored API key for one run

Watch Mode

Repeat the scan on a polling interval while you are iterating locally.

uv run --project apps/cli zerodaydb scan . --watch --interval 5

Supported Manifests

Node.js

package-lock.json, npm-shrinkwrap.json, package.json

Python

requirements*.txt, poetry.lock, Pipfile.lock, pyproject.toml

go.mod

Rust

Cargo.lock, Cargo.toml

Ruby, PHP, Java, and .NET manifests may be detected, but the current scanner does not produce findings for them yet.

Automation Ready

Structured JSON output and deterministic exit codes make the CLI easy to wire into existing build jobs.

Backed by Live Data

Each scan queries the same ZeroDayDB-backed package data exposed through the rest of the product.

More Than One Command

Use the same CLI for manifest scans, CVE lookups, free-text search, and authenticated sessions.

Ready to run a real scan?

Open the install guide for the current workspace command, or pair the CLI with the MCP server for AI-assisted workflows.

Pair with MCP

ZeroDayDB CLI

FREE

Run the Python CLI from a ZeroDayDB checkout to scan dependency manifests against live vulnerability data.

Practical Manifest Scanning

Point the CLI at a project directory and it will inspect supported manifests, query ZeroDayDB, and return a report you can use locally or in automation.

Supported Manifest Detection

Covers npm, Python, Go, and Rust manifests used by the current scanner.

Threshold-Based Exits

Use --fail-on to gate CI on severity.

Readable or JSON Output

Choose Rich tables for humans or --json for scripts.

Watch Mode

Repeat scans on a polling interval while you work.

Free to Use

The CLI is included at no extra cost. Today the supported path is the Python workspace command shown below, not a published npm or Homebrew package.

Why that matters: the commands on this page are meant to be run as-is. We would rather show the real entrypoint than a friendlier install story that does not exist yet.

Quick Scan

Scan the current directory for supported manifests.

uv run --project apps/cli zerodaydb scan .

Scan a Specific Directory

Point the CLI at any project directory instead of scanning your current working tree.

uv run --project apps/cli zerodaydb scan /path/to/project

Thresholds and Output

Use the flags the current scanner actually supports to tune exits and output formatting.

uv run --project apps/cli zerodaydb scan . --fail-on high # Fail when high-or-worse findings are present

uv run --project apps/cli zerodaydb scan . --json # Emit machine-readable output

uv run --project apps/cli zerodaydb scan . --api-key $ZERODAYDB_API_KEY # Override the stored API key for one run

Watch Mode

Repeat the scan on a polling interval while you are iterating locally.

uv run --project apps/cli zerodaydb scan . --watch --interval 5

Supported Manifests

Node.js

package-lock.json, npm-shrinkwrap.json, package.json

Python

requirements*.txt, poetry.lock, Pipfile.lock, pyproject.toml

go.mod

Rust

Cargo.lock, Cargo.toml

Ruby, PHP, Java, and .NET manifests may be detected, but the current scanner does not produce findings for them yet.

Automation Ready

Structured JSON output and deterministic exit codes make the CLI easy to wire into existing build jobs.

Backed by Live Data

Each scan queries the same ZeroDayDB-backed package data exposed through the rest of the product.

More Than One Command

Use the same CLI for manifest scans, CVE lookups, free-text search, and authenticated sessions.

Ready to run a real scan?

Open the install guide for the current workspace command, or pair the CLI with the MCP server for AI-assisted workflows.

Pair with MCP