Products / Intelligence

PIS - Pipeline Integrity Scanner

A ten-module build gate. Every scanner runs to completion, then the gate decides whether the merge is allowed.

PIS exists because a scanner that stops at the first finding tells you almost nothing. All ten modules run to full completion before the gate is evaluated, so one run gives the whole picture.

The gate blocks on critical and high findings and passes everything else, which keeps the rule simple enough that nobody argues with it. Reports are committed into the repository so the history of every decision is permanent.

Known transitive findings are suppressed through a per-repository allowlist rather than being ignored by hand.

Technical

  • Ten modules: SAST, security, dependencies, secrets, coverage, performance, infrastructure as code, containers, licensing, API contracts
  • Semgrep, Pylint, ESLint, Bandit, njsscan, pip-audit, npm audit, Trivy, Gitleaks, detect-secrets, Checkov, Hadolint, Dockle, Spectral
  • Gate blocks on critical or high, passes otherwise, evaluated only after all modules finish
  • Reports committed to .pis/reports/{year}/{month}/{run_id}-{sha}-{gate}.md
  • Dashboard ingestion through a Cloudflare Worker into D1
  • Per-repository allowlist for known transitive findings