Skip to main content
The kosli evaluate commands let you evaluate Kosli trails against custom policies written in . This is useful for enforcing rules like “every artifact must have an approved pull request” or “all security scans must pass”, and for gating deployments in CI/CD pipelines based on those rules. In this tutorial, you’ll write and evaluate policies against real trails in public Kosli orgs. Along the way, you’ll learn three design rules that prevent a Rego policy from granting false-positive compliance results.
1

Prerequisites

To follow this tutorial, you need to:
You don’t need OPA installed — the Kosli CLI has a built-in Rego evaluator. You just need to write a .rego policy file.
2

Write a policy

Create a file called pr-approved.rego with the following content:
pr-approved.rego
This policy applies three design rules that every evaluate policy should follow.Rule 1: default allow = false — fail safeTrails are denied unless the policy explicitly allows them. Anything the policy cannot positively verify is treated as non-compliant. This matches Kosli’s compliance direction: a false non-compliant blocks a good trail (recoverable); a false compliant passes a bad one (not recoverable).The alias pr_attestation_name := data.params.pr_attestation_name reads the attestation name from a params file rather than hardcoding it. Different orgs and flows use different names for their pull-request attestation (for example "pull-request" or "pr"). If the param is absent, pr_attestation_name is undefined, the lookup into attestations_statuses fails, trail_is_approved does not fire, and allow stays false — the correct fail-safe.Rule 2: Drive allow via a positive assertion, not the absence of violationsallow fires through trail_is_approved, which makes a positive claim: every PR has at least one approver. It is never driven by count(violations) == 0.The following pattern looks equivalent but is not safe:
If the violations rule body references a field that does not exist — a typo in pull_requests, an unexpected schema change, a missing key — the rule body silently produces no messages. The violations set is empty, count(violations) == 0 is true, and allow fires even though no PRs were actually checked. The trail receives a false-positive compliant result.With the safe pattern, if pull_requests is undefined, every pr in ... fails to evaluate, trail_is_approved does not fire, and allow stays false.Rule 3: Violations provide diagnostics onlyviolations explains why a policy was denied — it does not decide whether it was denied. When a violations rule body encounters an undefined reference, it silently produces no message. This is the safe failure mode: you lose a diagnostic, not a compliance check.
See the Rego Policy reference for the full policy contract, input data shape, and exit code behavior.
3

Evaluate multiple trails

Let’s evaluate several trails from the public cyber-dojo org against our policy. The kosli evaluate trails command fetches trail data from Kosli and passes it to the policy as input.trails:
The cyber-dojo project doesn’t require PR approvals, so you’ll see violations:
Now try the kosli-public org, where PRs do have approvers. This org names the attestation "pr":
4

Evaluate a single trail

The kosli evaluate trail (singular) command evaluates facts within a single trail. For example, you might check that a Snyk container scan found no high-severity vulnerabilities.Save this as snyk-no-high-vulns.rego:
snyk-no-high-vulns.rego
allow fires only when artifact_scan_is_clean succeeds for every artifact. If snyk-container-scan is absent or processed_snyk_results is undefined, artifact_scan_is_clean fails to fire and allow stays false.Use --attestations to enrich only the snyk data (faster than fetching all attestation details). The value uses the format artifact-name.attestation-type. Here, dashboard is the artifact name and snyk-container-scan is the attestation name:
The trail has zero high-severity vulnerabilities, so the policy allows it.
The input.trail / input.trails distinction and the full input data shape are documented in the Rego Policy reference.
5

Pass parameters to a policy

Policies often need thresholds that vary by environment — stricter in production than in staging. Use the --params flag to pass these values as data.params rather than hardcoding them in the policy.Save this as snyk-severity-threshold.rego:
snyk-severity-threshold.rego
Why the aliases at the top mattermax_high := data.params.max_high is not just shorthand. In the compliance path, result.high_count <= max_high is a positive bound check. If max_high is absent from the params file, this condition is undefined, artifact_within_threshold fails to fire, and allow stays false. That is the correct fail-safe behavior.Compare this to a policy that drives allow through the absence of violations:
If data.params.max_high is absent, the violations rule body fails silently, the set stays empty, and allow fires. A misconfigured params file grants compliance rather than denying it.Testing with kosli evaluate inputYou can test a policy locally without a real trail using kosli evaluate input. Create a minimal input file:
Evaluate with permissive staging thresholds:
Apply stricter production thresholds:
Now verify the fail-safe: omit max_high from params entirely:
allow is false even though no violation message was produced. The missing param causes the compliance check to fail, not to vacuously pass. Always verify this explicitly when writing a policy that relies on params.You can also load parameters from a file using the @ prefix:
The --params flag works the same way on kosli evaluate trail and kosli evaluate trails — parameters are always available as data.params in the policy.
6

Explore the policy input with --show-input

When writing policies, it helps to see exactly what data is available. Use --show-input combined with --output json to see the full input that gets passed to the policy:
This outputs the evaluation result along with the complete input object. You can pipe it through jq to explore the structure:
Use the --attestations flag to limit which attestations are enriched with full detail. The flag filters by attestation name (not type). For example, --attestations pull-request fetches only details for attestations named pull-request, which speeds up evaluation and reduces noise when exploring the input.
7

Use in CI/CD

The kosli evaluate commands exit with 0 on allow and 1 on deny or error — making them straightforward to use as pipeline gates. See the Rego Policy reference for details on distinguishing denial from command failure.
This pattern lets you enforce custom compliance rules as part of your delivery pipeline, using the same trail data that Kosli already collects.
8

Record the evaluation

After evaluating a trail, you can record the result as an attestation. This creates an audit record in Kosli that captures the policy, the full evaluation report, and any violations.This step requires write access to your Kosli org. The examples below use variables you’d set in your CI/CD pipeline. In your own pipeline you’d use your own policy file — here we use my-policy.rego as a placeholder:
This creates a generic attestation on the trail with:
  • --compliant set based on whether the policy allowed or denied — read directly from the JSON report rather than relying on the exit code, which avoids issues with set -e in CI environments like GitHub Actions
  • --attachments containing the Rego policy (for reproducibility) and the full JSON evaluation report (including the input data the policy evaluated)
  • --user-data containing the violations, which appear in the Kosli UI as structured metadata on the attestation
Use --compliant=value (with =) not --compliant value (with a space). Boolean flags in Kosli CLI require the = syntax when passing false — otherwise false is interpreted as a positional argument.

​
What you’ve accomplished

You have written OPA/Rego policies using the three design rules that prevent false-positive compliance results: fail-safe default, compliance via positive assertion, and violations as diagnostics only. You’ve evaluated Kosli trails against those policies, tested safety properties locally with kosli evaluate input, and recorded evaluation results as attestations. From here you can:
  • Explore evaluated trails in the Kosli app
  • Gate deployments in CI/CD pipelines using kosli evaluate trail exit codes
  • Use environment-specific params files to enforce different thresholds per environment
  • Extend your policies to check other attestation types. See kosli evaluate trail and kosli evaluate trails for the full flag reference
Last modified on June 5, 2026