Skip to main content

The open-source toolkit

SecureOps

Check for secrets and vulnerabilities as part of code review.

Open sourceMIT license

What it does

SecureOps brings Gitleaks, Trivy, and OSV-Scanner into a GitHub Actions workflow. It scans for exposed secrets, vulnerable dependencies, and infrastructure configuration issues. Read findings in pull request comments or export JSON, HTML, and SARIF reports.

What’s included

Secret Detection

Catch exposed API keys, passwords, and tokens before they reach production.

  • Powered by Gitleaks v8.28.0
  • Custom rule definitions via TOML configuration
  • Token masking in reports (first/last 4 chars)
  • Supports pre-commit and CI/CD scanning

Vulnerability Scanning

Find CVEs and security issues in dependencies and infrastructure code.

  • Trivy v0.65.0 for CVE and misconfiguration detection
  • OSV-Scanner v2.2.1 for open source vulnerability identification
  • Scans application dependencies, container images, and IaC
  • Fail-on-critical build policies

Reports in your workflow

Read findings in pull requests and the GitHub Security tab, or export reports for other tools.

  • JSON, HTML, and SARIF output formats
  • Automated PR comments with severity breakdown
  • GitHub Security tab integration via SARIF upload
  • Multi-factor risk scoring and assessment

Getting it running

01

Add the GitHub Action

Add SecureOps to your workflow YAML with a single step. Configure scan type, fail thresholds, and reporting options.

02

Scan on Every Push

SecureOps runs automatically on pushes and pull requests, scanning for secrets, vulnerabilities, and misconfigurations.

03

Review Findings

Findings appear as PR comments with severity levels and remediation guidance. Critical issues can block merges.

04

Org-Wide Audits

Run scheduled scans across your entire GitHub organization with consolidated dashboards and Slack summaries.

What it helps with

Check changes early

Run checks on pushes and pull requests. Configure required status checks to block merges when findings exceed your thresholds.

Start with the defaults

Add the action to your workflow, then adjust the scan types and failure thresholds to suit your repository.

Supply Chain Security

Tool downloads use SHA256 checksum verification. The scanner container runs as a non-root user.

Keep findings close to the code

Pull request comments include severity, context, and guidance so reviewers can investigate without leaving the workflow.

Built with

GitHub Actions Python Docker Gitleaks v8.28.0 Trivy v0.65.0 OSV-Scanner v2.2.1 SARIF

A few things you might be wondering

How do I add SecureOps to my repository?
Follow the workflow example in the linked GitHub repository. Configure the scan types, token permissions, failure thresholds, and reporting options for your project.
What types of security issues does SecureOps detect?
SecureOps detects three categories: secrets (API keys, tokens, passwords via Gitleaks), vulnerabilities (CVEs in dependencies via Trivy and OSV-Scanner), and infrastructure misconfigurations (in Terraform, Kubernetes manifests, etc.).
Can SecureOps scan my entire GitHub organization?
Yes. SecureOps supports organization-wide scanning with consolidated dashboards and Slack integration for summary reports across all your repositories.
Is SecureOps free for private repositories?
The code is free under the MIT license and supports public and private repositories. GitHub Actions usage is subject to your GitHub plan.
What report formats are supported?
SecureOps generates JSON (machine-readable), interactive HTML (human-readable), and SARIF (GitHub Security tab integration) reports.

A good place to start

Run SecureOps in your environment.

Start with the repository’s setup guide. If you’d like help adapting it to your environment, talk to us about what you need.