Tekton

Cloud-native security scanning with Tekton.

Warning Snippets on this page install the current CLI release rather than pinning one, so they do not go stale. If one no longer works, open an issue with the output of vulnetix --version.

Before You Start

Credentials come from A Secret referenced by env.valueFrom.secretKeyRef in the Task step.

Variable	Value
`VULNETIX_ORG_ID`	Organization UUID
`VULNETIX_API_KEY`	ApiKey hex digest

Environment variables authenticate on their own. Do not run vulnetix auth login on an ephemeral runner — see Authentication in CI/CD.

Quick Start

vulnetix-task.yaml:

apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: vulnetix-scan
spec:
  steps:
  - name: scan
    image: golang:1.21
    env:
    - name: VULNETIX_ORG_ID
      valueFrom:
        secretKeyRef:
          name: vulnetix-secrets
          key: org-id
    script: |
      go install github.com/vulnetix/cli/v3@latest
      vulnetix auth verify
      vulnetix scan --severity high

vulnetix auth verify on the first line fails the build immediately when the credential is missing or revoked, rather than halfway through a scan.

Note Tekton steps run in the same Pod, so install the CLI in the first step into a workspace and every later step can call it.

Running Individual Scans

Each subcommand runs standalone and uploads its own findings. Swap vulnetix scan for any of them:

vulnetix sca --severity high -o dist/sbom.cdx.json     # dependencies
vulnetix sast --severity high -o dist/sast.sarif       # source code
vulnetix secrets -o dist/secrets.sarif                 # hardcoded credentials
vulnetix license --allow MIT,Apache-2.0                # SPDX policy
vulnetix cbom --output-file dist/cbom.cdx.json         # cryptography, PQC posture
vulnetix aibom --output-file dist/aibom.cdx.json       # AI agents, SDKs, models

Note the flag split: the scan family takes -o <path>, while cbom, aibom, and malscan take --output-file. license takes neither. The full table is in the Subcommand Reference.

Keeping the Report

A shared workspace volume between steps.

The SARIF-producing scans write their file only when there are findings, so a clean run leaves nothing behind. Tolerate the missing path rather than failing on it.

Quality Gates

Gates are opt-in; without a gate flag the command reports and exits 0.

vulnetix scan --severity high --block-malware --block-eol --exploits active

To surface a breach without blocking the merge: Set the step’s onError: continue.

Full gate list in the Subcommand Reference.

Uploading Third-Party Artifacts

The scans upload themselves. upload is for reports produced by other tools:

vulnetix upload --file reports/semgrep.sarif --format sarif

Accepted formats: cyclonedx, spdx, sarif, openvex, csaf_vex.