Tool integration

Wapiti integration guide

Black-box Python web application vulnerability scanner with 30+ attack modules

Get a Free API Key

Integrate Wapiti with Vulnesis. Crawl and attack web applications to find SQL injection, XSS, XXE, SSRF, open redirects, and 30+ other vulnerability classes, then upload JSON reports.

PythonCLI toolJSONXMLHTML

Install & scan

$ # Recommended - ephemeral run, no global install
uv run --with wapiti3 wapiti --version

# Or install globally with pip
pip install wapiti3
$ uv run --with wapiti3 wapiti   -u https://example.com/   --scope folder   -f json   -o wapiti-report.json

Run Wapiti in CI

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

name: DAST – Wapiti
on:
  schedule:
    - cron: '0 2 * * 1'
  workflow_dispatch:
jobs:
  wapiti:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - name: Install uv
        uses: astral-sh/setup-uv@v4
      - name: Run Wapiti scan
        run: |
          uv run --with wapiti3 wapiti             -u ${{ secrets.TARGET_URL }}             --scope folder -f json -o wapiti-report.json
      - name: Upload report
        run: vulnetix upload --file wapiti-report.json

How Vulnesis compares: better together

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

Wapiti is strongest at its core category and also carries features in Network & Vulnerability Scanners, just as Vulnesis spans categories.

CapabilityVulnesisWapiti
Security coverage
SAST (static code analysis)✓ Built-in rules + Semgrep augmentation✗ Avoids source code by design; purely dynamic testing
SCA / dependencies✓ 40+ ecosystems, transitive graph✗ Explicitly no source-code or dependency analysis; black-box only
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine✓ Core black-box DAST: crawls and fuzzes running apps across 30+ attack modules
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~ Includes TLS/SSL misconfiguration checks against the live target
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 Wapiti does well

Where Vulnesis adds to it: Wapiti dynamically attacks a live application (SQLi, XSS, SSRF, XXE), testing Vulnesis does not perform, since it has no native DAST or fuzzing engine. Vulnesis ingests and orchestrates Wapiti's results, merging them with SAST, SCA, container, IaC, secrets and malware findings into a single deduplicated queue prioritised by exploit intelligence (EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV), with reachability, versioned VEX, Safe Harbour autofix and SSVC policy. Complementary: Wapiti runs the dynamic tests, Vulnesis consolidates and prioritises them across the whole program.

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

Upload Wapiti JSON, XML, HTML 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.

Wapiti documentation ↗  ·  Source repository ↗

Wire Wapiti into your CI/CD pipeline →