vulkro trends

Pro

vulkro trends is part of Pro: Trends (trends), how the risk moved between scans. On Free it stops before doing any work, prints what it needs and where to get it, and exits 1. See Pricing.

Show trend snapshots saved with vulkro scan --save. Track how finding counts move over time for a project. Included in the 14-day trial and in Pro.

Only scans run with --save are snapshotted, so run a few saved scans before expecting a trend.

Usage

vulkro trends [PATH]

Argument	Description	Default
PATH	Path to the project root.	.

Flags

Flag	Description	Default
--limit <LIMIT>	Maximum snapshots to show.	30

Examples

# Save a snapshot, then view the trend.
vulkro scan . --save
vulkro trends .

# Last 10 snapshots only.
vulkro trends . --limit 10

Related

• vulkro scan --save - record a trend snapshot.
• vulkro history - recent scan runs.
• vulkro usage - your local usage report.

Command reference

Generated from vulkro help trends 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.

[Pro] Show how findings have changed across saved scans.

[Pro] Show trend snapshots saved with `scan --save`.

Exit code: 0 on success (including no snapshots yet), 2 on database / IO error.

Usage: vulkro trends [OPTIONS] [PATH]

Arguments:
  [PATH]
          [default: .]

Options:
      --limit <LIMIT>
          [default: 30]

      --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')