Tool integration

Gitleaks integration guide

Git secret scanner with SARIF output

Get a Free API Key

Integrate Gitleaks with Vulnesis. Scan git repositories and directories for leaked secrets, API keys, and tokens.

CLI toolSARIF

Install & scan

$ go install github.com/zricethezav/gitleaks/v8@latest
$ gitleaks dir . -f sarif --report-path gitleaks.sarif

Run Gitleaks in CI

Scan on every push and upload the report as a workflow artifact:

- name: Install Gitleaks
  run: go install github.com/zricethezav/gitleaks/v8@latest
- name: Run Gitleaks
  run: gitleaks dir . -f sarif --report-path gitleaks.sarif
- name: Upload report
  uses: actions/upload-artifact@v6
  with:
    name: gitleaks
    path: gitleaks.sarif
    if-no-files-found: warn

Then one publish job hands every artifact in the run to Vulnesis, recorded under Gitleaks's own name and version. Written once per workflow, however many scanners you run:

publish:
  name: Publish to Vulnesis
  runs-on: ubuntu-latest
  needs: [scan]        # every scanner job, or its report is never published
  if: always()         # or one failing scanner suppresses all the others
  permissions:
    contents: read
    actions: read      # required to list the run's artifacts
  env:
    VULNETIX_ORG_ID: ${{ secrets.VULNETIX_ORG_ID }}
    VULNETIX_API_KEY: ${{ secrets.VULNETIX_API_KEY }}
  steps:
    - uses: actions/checkout@v5
    - name: Install Vulnesis CLI
      run: |
        curl -fsSL https://cli.vulnes.is/install.sh | sh -s -- --install-dir "$HOME/.local/bin"
        echo "$HOME/.local/bin" >> "$GITHUB_PATH"
    - name: Publish scanner reports
      env:
        GITHUB_TOKEN: ${{ github.token }}
      run: vulnetix gha upload --org-id "$VULNETIX_ORG_ID" --json

After the run, vulnetix gha status reports what was actually recorded.

How Vulnesis compares: better together

Vulnesis does not replace Gitleaks. Keep running it. Vulnesis sits on top of Gitleaks (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.

CapabilityVulnesisGitleaks
Security coverage
SAST (static code analysis)✓ Built-in rules + Semgrep augmentation✗
SCA / dependencies✓ 40+ ecosystems, transitive graph✗
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine✗
Container & image✓ Image CVEs, base image, Dockerfile✗
IaC / misconfiguration✓ Terraform, k8s, CloudFormation✗
Secret scanning✓ 1,000+ rules, source + binary + git history✓ Core: regex + entropy detection of hardcoded credentials across git history, files, archives; SARIF output
Cloud / CSPM✓ Cloud-posture findings, compliance tab✗
Mobile (MAST)~ Ingests mobile scanner output; no native mobile engine✗
License compliance✓ SPDX, copyleft/AGPL/SSPL policy✗
SBOM generation✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable✗
Malware / supply-chain✓ De-duplicated corpus + install-time firewall (25 registries)✗
Network / infra vuln~ Ingests network scanner output; no native network scanner✗
Fuzzing✗ Ingests fuzzing crashes; no native fuzzer✗
Pentest / bug bounty✗ Ingests pentest/bug-bounty findings; not a testing service✗
The Vulnesis orchestration layer
Cross-scanner dedup & one queue (ASPM)✓ Correlates every scanner into one prioritised queue with ownership routing✗
Exploit-intel prioritisation✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV✗
Reachability analysis✓ Tree-sitter + CVEAffected; direct/transitive/semantic✗
Versioned VEX + audit trail✓ Immutable OpenVEX/CycloneDX, cosign-signable✗
Safe Harbour autofix✓ Resolves + applies the nearest safe version✗
End-of-life policy✓ Flags/blocks past-EOL runtimes & packages✗
SSVC / risk-based policy✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets✗

✓ full · ~ partial · ✗ not covered

What Gitleaks does well

Where Vulnesis adds to it: Gitleaks is a best-in-class git secret finder but does regex/entropy only, no live-credential verification and no other scan class. Vulnesis ingests Gitleaks SARIF into one prioritised queue, deduplicates it against its own built-in secret scanner and its SAST/SCA/IaC/container/malware findings, and adds exploit-intel prioritisation, versioned VEX and SSVC that Gitleaks has no concept of. Better together: keep Gitleaks in pre-commit, let Vulnesis consolidate and triage.

No migration, no rip-and-replace. Gitleaks keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.

Centralise Gitleaks results in Vulnesis

Upload Gitleaks SARIF output to the Vulnesis platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.

Gitleaks documentation ↗  ·  Source repository ↗

Wire Gitleaks into your CI/CD pipeline →