How gigachad80/spectra works
Project type and purpose
• Spectra is an open-source, command-line Python tool for automated reconnaissance and sensitive-endpoint discovery.
• Its purpose is to orchestrate multiple external scanners (subfinder, httpx, waybackurls, gobuster, ffuf) plus built-in analysis and reporting, producing HTML/JSON/text outputs.
File structure
• Top-level files:
• spectra.py – the main Python entry point and orchestration script
• LICENSE, README.md – project metadata
• Directory:
• wordlists/ – contains sensitive_endpoints.txt for endpoint filtering
• No complex subdirectories or microservices—single-process CLI.
README for architectural clues
• Workflow phases described:
• Subdomain discovery
• Live host filtering
• Historical endpoint enumeration
• Brute-force scanning
• Analysis & categorization
• Reporting
• External dependencies: Golang tools and Python modules.
Main components
a. User Interface (CLI)
• Terminal/console invoking spectra.py
b. Orchestration Engine (spectra.py)
• Argument parsing & workflow selection
• Module invoker for each phase
c. External Scanning Tools
• subfinder
• httpx
• waybackurls
• gobuster / ffuf
d. Wordlist Store
• wordlists/sensitive_endpoints.txt
e. Analysis & Categorization Module
• HTTP status code analysis
• Vulnerability risk tagging
f. Reporting Module
• HTML renderer
• JSON/text writer
g. Output Workspace
• Directory structure for logs and reports
h. External Service
• Wayback Machine API (accessed by waybackurls)
Relationships and data flow
• CLI → Orchestration Engine
• Engine → subdomain discovery tool → raw domain list
• Raw list → httpx → filtered live hosts
• Live hosts → waybackurls → archived endpoints
• Live hosts + wordlists → gobuster/ffuf → discovered endpoints
• All endpoints → Analysis Module → categorized findings
• Findings → Reporting Module → output formats → Output Workspace
• Logs generated at each step for troubleshooting.
Architectural patterns and design principles
• Modular pipeline: each recon phase is a plug-and-play module
• Single responsibility: separate scanners, analyzers, reporters
• Extensibility: easy to swap or add new tools or wordlists
• CLI-driven configuration and interactive menu support.
Relevant technologies/frameworks
• Python 3.6+ (argparse or click)
• Golang-based external tools (subfinder, httpx, waybackurls, gobuster, ffuf)
• HTML templating library for reports (e.g., Jinja2)
• JSON library for structured output
• Logging module for detailed logs
Key elements to capture
• Components: CLI, orchestration engine, each scanner, analysis, reporting, data stores
• Flows: raw data ingestion, filtering, enrichment, analysis, output
• External dependencies: tool binaries, API calls
• Output targets: HTML, JSON, text, logs