Skip to main content

vulkro usage

Show your own local scan-history report: scans over time, findings by severity, codebase size (LOC), and your most-scanned projects. Read entirely from your local database. This command is 100% local and makes no network calls: it never triggers the anonymous heartbeat and runs fine air-gapped.

Only scans run with vulkro scan --save are recorded in the history this report reads.

Usage

vulkro usage # text summary of your local scan history
vulkro usage --json # same report as JSON, for export or piping

Flags

FlagDescription
--jsonEmit the report as JSON instead of the text summary (for export or piping into another tool).

Exit codes

  • 0 report printed (or there is no history yet).
  • 2 error: the local database could not be read.

Command reference

Generated from vulkro help usage on vulkro 0.26.0. This block is the authoritative flag, usage, and exit-code reference for this command; the prose above is the friendly explanation. Do not edit this block by hand; run npm run docs:cli after a release.

Show your own scan history and usage, read from the local database only.

Show your own local scan-history report: scans over time, findings by severity, codebase size (LOC), and your most-scanned projects. Read entirely from `~/.vulkro/scans.db`. This command is 100% local and makes no network calls (it never triggers the anonymous heartbeat).

Exit codes: `0` report printed (or no history yet); `2` error (cannot read the local database).

Usage: vulkro usage [OPTIONS]

Options:
--json
Emit the report as JSON instead of the text summary (for export or piping into another tool)

--offline
Hard-disable every outbound network call for this run (sets VULKRO_OFFLINE=1). Blocks the CVE feed, the license heartbeat, the update check, webhooks, and any cloud AI endpoint; a loopback model (http://127.0.0.1, http://localhost) is still allowed. Equivalent to exporting VULKRO_OFFLINE=1, and the flag wins when both are set

-h, --help
Print help (see a summary with '-h')