Integrate cppcheck with Vulnesis. Detect bugs, undefined behaviour, and security issues in C/C++ code with SARIF output.
Install & scan
$ uv run --with cppcheck cppcheck --version $ uv run --with cppcheck cppcheck --output-format=sarif --output-file=cppcheck.sarif src/
Run cppcheck in CI
Scan on every push and upload the report as a workflow artifact:
- name: Run cppcheck
run: |
pip install cppcheck
cppcheck --output-format=sarif --output-file=cppcheck.sarif src/
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: cppcheck
path: cppcheck.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under cppcheck'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" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnesis compares: better together
Vulnesis does not replace cppcheck. Keep running it. Vulnesis sits on top of cppcheck (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
cppcheck is strongest at its core category and also carries features in Compliance & Policy Engines, just as Vulnesis spans categories.
| Capability | Vulnesis | cppcheck |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✓ Core: undefined-behaviour, memory, buffer and pointer bug detection for C/C++ (docs) |
| 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 cppcheck does well
- Deep C/C++ analysis that works without a full build environment and tolerates non-standard/embedded syntax
- Bidirectional data-flow analysis with a design goal of very few false positives - trusted enough to be run in strict CI gates
- Catches real memory-safety CVE classes: buffer overflows, null-pointer dereference, uninitialized variables, integer overflow, use-after-free, resource/FD leaks
- Standards compliance for safety-critical code via the free misra.py addon (MISRA C 2012); Premium extends to MISRA C++, CERT C/C++ and AUTOSAR
Where Vulnesis adds to it: Vulnesis does SAST but does not run cppcheck's C/C++ memory-safety or MISRA/CERT analysis; the two do not overlap on that native depth. Better together: Vulnesis ingests cppcheck SARIF/XML output into its single deduplicated queue and adds what cppcheck has no concept of - cross-scanner correlation, EPSS/KEV/LEV exploit-intel prioritisation, reachability, versioned VEX + audit, and SSVC/EOL policy.
No migration, no rip-and-replace. cppcheck 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 cppcheck results in Vulnesis
Upload cppcheck 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.