Integrate Flawfinder with Vulnesis. Scan C and C++ code for potential security flaws and upload SARIF results.
Install & scan
$ uv run --with flawfinder flawfinder --version $ uv run --with flawfinder flawfinder --sarif . > flawfinder.sarif
Run Flawfinder in CI
Scan on every push and upload the report as a workflow artifact:
- name: Run Flawfinder
run: |
pip install flawfinder
flawfinder --sarif . > flawfinder.sarif
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: flawfinder
path: flawfinder.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under Flawfinder'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 Flawfinder. Keep running it. Vulnesis sits on top of Flawfinder (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
| Capability | Vulnesis | Flawfinder |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✓ Core: lexical pattern match of C/C++ source against a built-in dangerous-function database; no data/control-flow analysis |
| 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 Flawfinder does well
- Fast, dependency-free lexical scan of C/C++ that instantly flags dangerous function usage (strcpy, sprintf, gets, format strings, race conditions)
- Findings ranked by risk level (factoring the function and its arguments) with CWE mapping and hit-density metrics
- Simple by design and CWE-compatible, with SARIF/CSV/HTML output that slots into pipelines and legacy codebases with no build step
- Long-standing, transparent open-source tool useful as a quick first pass before deeper C/C++ analysis
Where Vulnesis adds to it: Flawfinder is a naive lexical C/C++ scanner (no data-flow, source-only). Vulnesis does not replace its C/C++ heuristics but ingests its SARIF output, deduping it into a single prioritised queue and layering exploit-intel, reachability, versioned VEX + audit, SSVC and autofix, turning raw flagged function calls into triaged, evidence-backed findings.
No migration, no rip-and-replace. Flawfinder 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 Flawfinder results in Vulnesis
Upload Flawfinder 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.