Skip to main content

vulkro-sf trends

Tracks how your findings move over time. A single scan tells you where the org stands today; trends tells you which direction it is going. It reads a series of stored scan results and reports whether debt is accumulating or being paid down, broken out by finding class, surface, and severity. This is the artifact for a quarterly health review or a "are we getting better" conversation with leadership.

Runs over stored scan history on the local machine. No org connection is required.

Synopsis​

vulkro-sf trends [flags]

Flags​

FlagTypeDefaultDescription
--history <path>string.vulkro-sf/historyDirectory of stored scan-result files to compute the trend from.
--since <date>string(all)Limit the trend window to scans on or after this ISO date (YYYY-MM-DD).
--format <fmt>enumtableOutput format: table (human-readable trend summary) or json (machine-readable trend series, for a dashboard or a slide).

Exit codes​

  • 0 - the trend was computed and finding counts are flat or improving over the window.
  • 1 - the trend was computed and finding counts regressed over the window (debt increased).
  • 2 - error: no readable history under --history, a stored result could not be parsed, or an internal error. The message names the cause and the next step.

What it does​

trends loads each stored scan result in the history directory, orders them by scan date, and computes the delta series:

  • Total findings over time, so the headline direction is clear.
  • Per-surface trend (Apex, Flow, LWC, metadata, and the rest), so a regression can be traced to where it is happening.
  • Per-severity trend, so a rising Critical count is not hidden by a falling Informational count.
  • New, resolved, and persistent finding counts between the first and last scan in the window.

The table format is the at-a-glance read; the json format is the series you chart on a dashboard or paste into a quarterly review.

Example​

# Trend over all stored scans.
vulkro-sf trends

# Trend since the start of the quarter, as JSON for a dashboard.
vulkro-sf trends --since 2026-04-01 --format json > trends.json

# Trend from a custom history directory.
vulkro-sf trends --history ./scan-archive