Tool integration

GCC integration guide

GCC 13+ static analyzer with native SARIF diagnostic output

Get a Free API Key

Integrate GCC static analysis with Vulnesis. Use GCC 13+ SARIF output to capture compiler warnings and -fanalyzer findings in a format Vulnesis can ingest.

C / C++ / FortranCLI toolSARIF

Install & scan

$ # Ubuntu/Debian (GCC 13+)
sudo apt-get install gcc-13 g++-13

# macOS via Homebrew
brew install gcc

# Verify version (need 13+ for SARIF)
gcc --version
$ # SARIF output to a file (named <source>.sarif automatically)
gcc-13 -fanalyzer -fdiagnostics-format=sarif-file -Wall -Wextra myfile.c

# Or emit SARIF to stderr and redirect
gcc-13 -fanalyzer -fdiagnostics-format=sarif-stderr -Wall myfile.c 2> gcc.sarif

Run GCC in CI

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

- name: Install GCC 13
  run: sudo apt-get install -y gcc-13

- name: Run GCC Static Analyzer
  run: |
    find src/ -name "*.c" | xargs -I{} gcc-13       -fanalyzer -fdiagnostics-format=sarif-file       -Wall -c {} -I include/ 2>/dev/null || true

- name: Upload to Vulnesis
  run: |
    for f in src/*.sarif; do vulnetix upload --file "$f"; done

How Vulnesis compares: better together

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

CapabilityVulnesisGCC
Security coverage
SAST (static code analysis)✓ Built-in rules + Semgrep augmentation✓ Core: -fanalyzer static analysis (mainly C; C++ experimental) with native SARIF output; strong memory-safety and taint checks
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✗
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 GCC does well

Where Vulnesis adds to it: Vulnesis ingests GCC's SARIF diagnostics and folds them into the cross-scanner dedup queue, adding exploit-intel prioritisation, reachability, VEX and SSVC. It consolidates GCC's compiler-level findings; it does not run or replace the -fanalyzer pass.

No migration, no rip-and-replace. GCC 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 GCC results in Vulnesis

Upload GCC 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.

GCC documentation ↗  ·  Source repository ↗

Wire GCC into your CI/CD pipeline →