ZipLoom
Home
PricingSign InGet Your Live URL

security

GitHub Actions Integration

ziploom/scan-action Gates Every Merge — Security In The Pipeline, Not Just At Deploy.

Updated

At a glance

The ziploom/scan-action runs a security scan on every pull request. Configure fail-on: high to block merges when critical vulnerabilities are detected.

  • Shift-Left Security
  • Configurable Fail Conditions
  • No CI Credentials To Manage
Sample. ziploom/scan-action scans every pull request at its exact commit and reports as a check. Findings at or above your fail-on level fail the check; a scan error fails closed, never open.

Why it matters

A deploy gate catches a problem at the last possible moment, after the code is merged. The GitHub Action moves the same scan into the pull request, where a fix is a commit on a branch rather than a hotfix on production.

It also looks at the pipeline itself. Workflows run with credentials for your repository and often for production, and they run automatically, sometimes on code from a fork. Over-broad token permissions, actions pinned to a tag that can be moved, and secrets exposed to forked pull requests are each a path into both. The action pins the scan to the exact commit, authenticates with a scan-only key stored hashed, and fails closed: a scan that errors never reads as a pass.

The Scan Inside Your Pull RequestIllustration · sample data
pull requestScan this commitscan-only keyworkflow.ymlpermissions · pinsZipLoom scanerror = failednever read as a pass

What you get

Shift-Left Security

A vulnerability caught in CI is cheaper to fix than one caught in production. The GitHub Actions integration runs the same security scan as the deploy-time check, but earlier — in the pull request, before the code is merged.

Configurable Fail Conditions

fail-on: high blocks the merge on critical vulnerabilities. fail-on: medium is more conservative. fail-on: none runs the scan for visibility without blocking. Each PR gets a scan report in the Actions tab.

No CI Credentials To Manage

The action authenticates to ZipLoom with an organization CI key — scan-only, stored hashed, revocable in one click. No Snyk token, no Grype installation, no vulnerability database to update. The scan infrastructure is hosted by ZipLoom.

Setup

  1. 1

    Generate a key in Settings → API Keys (type: CI / GitHub Action).

  2. 2

    Add it to your GitHub repository as a secret named ZIPLOOM_API_KEY.

  3. 3

    Add the action to your workflow: `uses: ziploom/scan-action@v2` with your project ID and fail-on setting. It pins the scan to the exact commit and exits 0 (pass), 1 (findings at or above fail-on), 2 (scan error) or 3 (configuration error) — it fails closed, never open.

  4. 4

    Every pull request now gets a security scan. Results appear as a check in the PR status.

What this check inspects

  • Workflow permissions — the default write-all token scope that turns a pull request into a supply-chain risk.

  • Third-party actions pinned to a moving tag rather than a commit SHA.

  • Secrets exposed to workflows triggered by pull requests from forks.

  • Steps that echo environment variables or tokens into build logs.

What it means when this fails

Your CI pipeline has credentials for your repository and often for production. A compromised or over-permissioned workflow is a direct path to both, and it runs automatically on code you didn't write when the trigger comes from a fork.

What it does not do

  • It does not edit your workflow files. It reports the finding and the fix; you apply the change.

  • A CI key can only start scans. It cannot reach the MCP endpoint or anything else in your account.

Questions

Why does pinning an action matter?
A tag can be moved to point at new code. Pinning to a commit SHA means the action you reviewed is the action that runs.
Is this the same as scanning my app code?
No. This is the pipeline that builds and ships the app — a separate attack surface with its own credentials.
Does it change my workflows?
It reports the findings and the fix. You apply the change.

What it replaces

GitHub Advanced Security (both)

Code Security + Secret Protection together, per active committer.

$49/committer/mo

Snyk Team

Per contributing developer, 5-seat minimum (~$1,500/yr entry). Code + dependency scanning; does not deploy your app.

$25/dev/mo

Semgrep Team

SAST with a strong free OSS engine; rules and triage are yours to maintain.

$35/contributor/mo

ZipLoom Solo — every deploy check included

Deploy, security scan, and monitoring in one flat price. Guild $40/mo · Studio $70/mo · LoomWorks $149/mo · Business $299/mo.

$216/yr($20/mo)

Related features