vulkro ci

Write a CI-friendly Markdown report of endpoints, findings and, if you pass a base ref, what changed in the API surface.

vulkro login                                    # uses VULKRO_ACCOUNT_TOKEN in CI
vulkro ci . --base origin/main -o vulkro-ci.md

Attach the report to the job or post it as a pull request comment. In CI, set VULKRO_ACCOUNT_TOKEN from a secret holding a CI key from the portal. An air-gapped runner sets VULKRO_LICENSE_B64 to a base64 .lic file instead. See CI keys.

Flags

Flag	Description
[PATH]	Project root. Default ..
--base <REF>	Add a surface diff against this git ref.
-o, --output <FILE>	Write to a file instead of stdout.

Exit codes

Code	Meaning
0	Report written, no Critical or High findings.
1	Report written, at least one Critical or High finding.
2	Bad base ref, scan or IO error. Also 2 when no source file could be read and nothing was reported.

See also: vulkro gate, CI/CD integration.