Documentation Index
Fetch the complete documentation index at: https://mintlify.com/NetRiseInc/provenance-cli/llms.txt
Use this file to discover all available pages before exploring further.
provenance check is the primary CI/CD integration point. It evaluates a single package or all packages in an SBOM against one or more YAML policy files and returns a semantic exit code indicating whether the target passes, requires review, or is denied by policy.
All packages are evaluated concurrently.
provenance check accepts the global flags --format (human, json, sarif), --quiet, --no-color, --ascii, and -v/-vv. Use --format sarif to produce SARIF v2.1.0 output for GitHub Code Scanning and other SARIF-compatible tools.Synopsis
TARGET argument is either:
- A PURL starting with
pkg:— evaluates a single package. - A path to an SBOM file — auto-detected if the path exists on disk. All packages in the SBOM are evaluated.
Flags
Path to a policy YAML file. Can be specified multiple times to apply several policies together. All rules from all specified files are combined and evaluated as a single policy set.
Path to a directory of policy YAML files (
.yaml or .yml). All files in the directory are loaded. Can be used alongside --policy.Exit codes
| Code | Verdict | Meaning |
|---|---|---|
0 | PASS | All checks passed (only warn or info findings, or no findings). |
1 | DENY | At least one deny rule matched. |
2 | REVIEW | No deny findings, but at least one review rule matched. |
3 | ERROR | Runtime error — network failure, authentication error, parse error, etc. |
allow rules are evaluated first. If a package matches an allow rule, it is exempted from all deny, review, and warn rules in the same policy set. This lets you carve out known-good packages from broad rules.Examples
Check a single package against a policy fileRelated
Policy engine
Write YAML policy files to define rules, conditions, and actions.
Exit codes
Full reference for exit code semantics and CI/CD integration patterns.