Integrate GCC static analysis with Vulnetix. Use GCC 13+ SARIF output to capture compiler warnings and -fanalyzer findings in a format Vulnetix can ingest.
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 Vulnetix
run: |
for f in src/*.sarif; do vulnetix upload --file "$f"; done
How Vulnetix compares: better together
Vulnetix does not replace GCC. Keep running it. Vulnetix sits on top of GCC (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
| Capability | Vulnetix | GCC |
|---|---|---|
| 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 Vulnetix 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, Vulnetix 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
- -fanalyzer runs coverage-guided symbolic execution during compilation, detecting use-after-free, double-free, memory/fd leaks, buffer overflows and null derefs interprocedurally
- Built-in taint analysis tracks attacker-controllable values into division, array indexing and allocation sizes
- Native SARIF diagnostic output since GCC 13 (-fdiagnostics-format=sarif-file), refined in GCC 15 with multiple output sinks
- Zero extra tooling: security analysis runs as part of the compiler the project already uses
Where Vulnetix adds to it: Vulnetix 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; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise GCC results in Vulnetix
Upload GCC SARIF output to the Vulnetix 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.