Security scanning inside
the pipeline you already use.

Trigger Strata's repository scan automatically from GitHub Actions or GitLab CI — on every push, every pull request, or a schedule. Catch hardcoded secrets, vulnerable dependencies, and SAST findings before they merge, not after they ship.

GitHub Actions & GitLab CI
API key + outbound webhooks
Push, PR, or scheduled
Runs on the event that fits your workflow
Configurable thresholds
Choose which severities fail the build

Catch it at the pull request, not after deploy

Software supply chain risk enters through the pipeline

A hardcoded credential, a newly vulnerable dependency, or an unsafe code pattern is far cheaper to catch in a pull request than after it has merged, deployed, and shipped to production. Manual, scheduled reviews still leave a gap — anything merged between reviews ships unscanned.

Running the scan as part of the pipeline closes that gap: every change is assessed before it reaches the main branch, using the same checks whether the scan was triggered by a person or by a pipeline event.

Every pull request scanned before merge, not just at release time
New dependency CVEs caught the moment a manifest changes
One scan engine — dashboard and pipeline results are the same data
Pull Request #482 — checks
FAILED
strata-security-scan
1 critical finding — hardcoded API key
PASSED
unit-tests
142 passed
PASSED
lint
no issues

GitHub Actions and GitLab CI

Add one step to a workflow you already have — there's no separate CI/CD product to adopt, just a scan step inside your existing pipeline.

🐙

GitHub Actions

Trigger a scan as a step in any workflow: on pull_request, push, or a schedule trigger. The API key is stored as a repository secret and referenced in the workflow, never hardcoded. Pull requests from forks do not receive repository secrets, so the generated workflow cannot scan them.

🦊

GitLab CI

Add a job to .gitlab-ci.yml that runs on branch, merge request, and scheduled pipelines. The API key is stored as a masked GitLab CI/CD variable.

🔔

Outbound webhooks

Get a scan.complete or scan.failed event for pipeline scans, independent of the pipeline step itself. Point it at your own endpoint to route results to a ticketing system or a separate dashboard.

From API key to blocked merge

01

Generate an API key

Create an API key for your account from the dashboard. Store it as a repository or CI/CD secret (a GitHub Actions secret or GitLab CI/CD variable), never in the workflow file itself.

02

Add a scan step to your pipeline

Add the generated step to your existing workflow. It calls the Strata API with the key, and Strata clones the repository itself (private repositories through your connected GitHub or GitLab account). No agent to install, no infrastructure to provision.

03

Scan runs on push, PR, or schedule

The generated GitHub Actions workflow runs on pull requests and on pushes to main or master; the GitLab job runs on branch and merge request pipelines. Add a schedule trigger if you also want nightly runs. The same repository scan runs each time: secrets, sensitive files, SAST, and dependency CVEs.

04

Fail the build on the severities you choose

The fail_on list in the pipeline step sets which severities fail the job (Critical by default). Outbound webhooks can also notify your own service when a pipeline scan completes or fails.

05

Track results across every run

Every pipeline-triggered scan appears in the same risk dashboard as manual scans, with full findings history and lifecycle tracking — not a separate CI-only view you have to check independently.

REST API access, including CI/CD triggers, is included on the Team plan. See plan details →

The same four passes, automatically

A pipeline-triggered scan runs the identical engine as a manual repository scan — hardcoded secret detection, sensitive file detection, SAST pattern matching for injection and unsafe code, and dependency CVE lookups against the OSV.dev database. Nothing about the checks themselves changes based on what triggered the scan.

Common Questions

No. The scan step calls the Strata API directly from your existing GitHub-hosted or GitLab-hosted runner (or a self-hosted one, if that's what you already use) — there is no separate agent to install or infrastructure to provision.
The same repository scan available from the dashboard — secrets, sensitive files, SAST pattern matching, and dependency CVE lookups. See the repository security scanner page for the full breakdown of what each pass checks.
Yes. The pipeline step sends a fail_on list, for example critical and high. The job fails when the scan finds any finding at one of those severities; severities left off the list do not fail the build.
It's the same scan engine — the only difference is what triggers it. A manual scan is started by a person; a CI/CD-triggered scan is started automatically by a pipeline event (push, pull request, or schedule) via an API key.

See Strata in action

Watch a walkthrough of the platform — from upload to full security report.

Demo video coming soon

Get a personalized walkthrough of Strata — we will cover your specific workflow live.

Request a Demo →

Add a scan step
to your next pipeline run.

Start free to explore repository scanning from the dashboard, then upgrade to Team for API access and CI/CD triggers.

Review your pipeline against a checklist: try the Secure SDLC Planner.