How qyvora/qyvora-anansi works
ANANSI is a terminal attack-surface reconnaissance CLI: a user supplies a domain, the CLI orchestrates discovery and live-host checks, performs security and stack audits, correlates findings into exploit chains, and renders reports. The README documents ten phases; the graph preserves those stages and the separate active-exploitation command. Groups reflect the CLI, recon pipeline, assessment stages, and output/exploitation layers. Some phase wiring is explicit in the README or root excerpt; unsampled implementation details are not inferred beyond documented relationships.
Main entry points: root.go Scan commands · httpclient.go HTTP transport · discovery.go Subdomain discovery · engine.go Exploit engine
Components 22
CLI orchestration
- Program entry
main.go - Scan commands
cmd/root.go - Exploit command
cmd/exploit.go - Update command
cmd/update.go
Host reconnaissance
- Subdomain discovery
internal/discovery/discovery.go - HTTP probing
internal/probe/probe.go - HTTP transport
internal/httpclient/httpclient.go - DNS cache
internal/dnscache/dnscache.go
Security assessment
- TLS analysis
internal/tls/tls.go - Header audit
internal/headers/headers.go - Exposed paths
internal/paths/paths.go - Stack audit
internal/techstack/techstack.go - Takeover checks
internal/takeover/takeover.go - OSINT collection
internal/osint/osint.go
Findings and actions
- Exploit chains
internal/chain/chain.go - Exploit engine
internal/exploit/engine.go - Exploit modules
internal/exploit/modules.go - Module registry
internal/exploit/registry.go - Report renderer
internal/output/terminal.go - Event stream
internal/events/events.go - Self updater
internal/selfupdate/selfupdate.go
Other components
- Operator
Connections 30
- Operator → Program entry: starts
README.md - Program entry → Scan commands: delegates
main.go - Scan commands → Subdomain discovery: runs phase
cmd/root.go - Scan commands → HTTP probing: runs phase
README.md - Scan commands → TLS analysis: runs phase
cmd/root.go - Scan commands → Header audit: runs phase
README.md - Scan commands → Exposed paths: runs phase
README.md - Scan commands → Stack audit: runs phase
README.md - Scan commands → Takeover checks: runs phase
README.md - Scan commands → OSINT collection: runs phase
cmd/root.go - Scan commands → Exploit chains: assembles findings
cmd/root.go - Scan commands → Report renderer: renders results
cmd/root.go - Scan commands → Event stream: emits events
cmd/root.go - Scan commands → Exploit command: offers command
- Exploit command → Exploit engine: runs engine
cmd/exploit.go - Exploit engine → Exploit modules: dispatches modules
- Exploit engine → Module registry: uses registry
- Subdomain discovery → DNS cache: resolves via
internal/discovery/discovery.go - TLS analysis → Subdomain discovery: adds SAN hosts
README.md - Scan commands → HTTP probing: selects live hosts
cmd/root.go - Scan commands → Takeover checks: checks candidates
README.md - Subdomain discovery → Report renderer: reports progress
internal/discovery/discovery.go - HTTP probing → HTTP transport: creates client
internal/probe/probe.go - Exposed paths → HTTP transport: uses transport
internal/paths/paths.go - Header audit → HTTP transport: uses transport
internal/headers/headers.go - Stack audit → HTTP transport: uses transport
internal/techstack/techstack.go - Takeover checks → HTTP transport: uses transport
internal/takeover/takeover.go - OSINT collection → HTTP transport: uses transport
internal/osint/osint.go - Report renderer → Operator: prints report
README.md - Update command → Self updater: invokes update
cmd/update.go