Skip to main content
Vigolium Workbench Dashboard
Vigolium can operate as a CLI tool for one-off scans, as a persistent REST API server that ingests live traffic, or as a standalone ingestor client that forwards traffic to a running server. All scan data is project-scoped for multi-tenancy support. Module: github.com/vigolium/vigolium, requires Go 1.26+.

Operating Modes

ModeBinaryDescription
CLI Scannervigolium scanRun scans directly from the command line against targets, input files (OpenAPI, Postman, Burp, cURL, HAR), or source code paths.
Server Modevigolium serverLaunch a REST API server with Swagger UI. Ingest traffic, trigger scans, query findings, and run agent sessions over HTTP.
Ingestor Clientvigolium-ingestorLightweight client that captures and forwards HTTP traffic to a running Vigolium server for analysis.

Scanning Paradigms

Native Scan

The native scan pipeline is fully deterministic -pure Go, no AI involvement. Requests flow through a fixed sequence of phases, each handling a distinct stage of reconnaissance or testing. Phases (in order):
Heuristics -> External Harvesting -> Spidering -> SAST -> Discovery -> KnownIssueScan -> Audit -> Extension
PhasePurpose
HeuristicsLightweight fingerprinting and technology detection
External HarvestingWayback Machine and other passive source enumeration
SpideringActive crawling, JS analysis, link and form extraction
SASTStatic analysis of source code (when --source is provided)
DiscoveryEndpoint and content discovery via wordlists
KnownIssueScanChecks for known CVEs and common misconfigurations
AuditCore vulnerability testing -injection, XSS, SSRF, etc.
ExtensionUser-supplied JavaScript scanning extensions
Strategies control which phases run and how aggressively:
StrategyBehavior
LiteFast surface-level scan; skips heavy crawling and discovery
BalancedDefault. Runs all phases with sensible limits
DeepExhaustive scanning with higher limits and broader wordlists
WhiteboxSource-aware scanning with route extraction and SAST integration

Agentic Scan

Agentic scanning uses AI agents to drive or augment the scanning process. Invoked via vigolium agent <mode>. Supports Claude, Codex, Gemini, and OpenCode backends.
ModeCommandDescription
Queryvigolium agent querySingle-shot prompt execution. Good for code review, endpoint discovery, secret detection. No network scanning.
Autopilotvigolium agent autopilotThe AI agent drives the CLI autonomously through a sandboxed terminal (ACP protocol). It can run scans, inspect results, and iterate.
Swarmvigolium agent swarmMulti-phase pipeline where native Go handles heavy lifting and AI intervenes at checkpoints -planning attacks, triaging results, and generating custom JS scanner extensions.
All agent modes support --source for source-aware analysis and store session artifacts (plans, extensions, output) in a configurable sessions directory.

Architecture at a Glance

                          +------------------+
                          |   Input Sources   |
                          | curl/OpenAPI/Burp |
                          |  HAR/Postman/URL  |
                          +--------+---------+
                                   |
                    +--------------+--------------+
                    |                             |
              vigolium scan                 vigolium server
                    |                             |
                    v                             v
            +---------------+           +-----------------+
            |  Scope Filter |           | REST API (Fiber)|
            +-------+-------+           +--------+--------+
                    |                             |
                    +-------------+---------------+
                                  |
                    +-------------+-------------+
                    |                           |
              Native Scan                 Agentic Scan
                    |                           |
         +----------+----------+      +---------+---------+
         |  Executor (Workers) |      |   Agent Engine    |
         |  Rate Limiter       |      |   ACP / Terminal  |
         +----------+----------+      |   Prompt Templates|
                    |                 +---------+---------+
         +----------+----------+                |
         |  Module Registry    |      +---------+---------+
         |  127 Active Modules |      | AI Backend        |
         |   83 Passive Modules|      | Claude/Codex/     |
         +----------+----------+      | Gemini/OpenCode   |
                    |                 +---------+---------+
                    +-------------+---------------+
                                  |
                    +-------------+-------------+
                    |       Results Store       |
                    |  SQLite / PostgreSQL      |
                    |  HTML / JSONL / Console   |
                    +---------------------------+

Reading Guide

I want to…Go to
Get up and running quicklygetting-started
Understand the native scan pipelinenative-scan/how-it-works
Choose a scanning strategynative-scan/strategies
Learn about individual scan phasesnative-scan/phases/ (discovery, spidering, audit, extension, spa)
Explore agentic scanningagentic-scan/agent-mode
Use Autopilot modeagentic-scan/autopilot
Use Swarm modeagentic-scan/swarm
Use Query modeagentic-scan/query
Run Vigolium as a serverserver-mode/
Configure scans and settingsconfiguration
Format and export resultsoutput-and-reporting
Write custom JS extensionscustomization/writing-extensions
Build from sourcedevelopment/building
Develop new scanner modulesdevelopment/developing-modules
Browse the REST APIapi-references/
Manage projects (multi-tenancy)projects
Debug issuestroubleshooting
Vigolium Overview
Getting Started
Configuration
Scanning Modes
Strategies
Authentication
Discovery
Spidering
Audit
Agent Mode
Autopilot
Swarm
Server Mode
Output & Reporting
Writing Extensions
Whitebox Scanning
CI/CD Integration
REST API Reference