vulkro notify
POST a scan summary to a webhook (Slack, Teams, or a generic JSON
receiver). This is opt-in network egress: it is the one place notify
touches the network, and only when you invoke it. Included in the 90-day
trial and in Pro.
For richer routing (Jira issues, PagerDuty incidents) attached to a scan,
see the scan --post-to flag on vulkro scan.
Usage
vulkro notify [PATH] --url <WEBHOOK_URL>
| Argument | Description | Default |
|---|---|---|
PATH | Path to the project root. | . |
Flags
| Flag | Description | Default |
|---|---|---|
--url <URL> | Webhook URL (Slack, Teams, or a generic JSON receiver). Required. | |
--min-severity <MIN_SEVERITY> | Only notify if this severity or worse is present. | high |
Example
vulkro notify . --url "$SLACK_WEBHOOK" --min-severity critical
Payloads carry only severity counts, short signal IDs, workspace-relative paths, line numbers, and truncated messages: no absolute paths and no code snippets.
Related
vulkro scan --post-to- Slack / Teams / Jira / PagerDuty after a scan.- CI/CD integration - wiring alerts into pipelines.