Self-coordinating Penetration and Exploit Crew for Threat Research and Exposure
Multi-agent GitHub repository security audits with a live dashboard — scope-controlled and observable end to end.
Important
SPECTRE audits only repositories you own or have explicit permission to test.
Every engagement requires a scope allowlist (scopes/*.yaml). Do not scan
arbitrary public repos without authorization.
- Four-agent crew — Recon, VulnHunter, Exploiter, and Reporter coordinate through a shared Findings Bus
- Live dashboard — Watch findings, handoffs, and report sections stream in real time
- Sandboxed tools — GitHub API, gitleaks, osv-scanner, and workflow checks with timeouts and redaction
- Safety by default — Repo allowlists, audit logs, and an engagement kill switch
Requirements: Docker with Compose, a GitHub token, and an LLM API key (Groq by default).
cp .env.example .env
# Set GITHUB_TOKEN and GROQ_API_KEY in .env
docker compose up --buildOpen http://localhost:8080 and choose Start audit.
| Port | Service |
|---|---|
8080 |
Demo dashboard |
8765 |
WebSocket control plane |
Optional CLI helpers (reports, halt, sessions):
docker compose --profile cli run --rm cli sessionsFull details: Docker guide.
| Variable | Purpose |
|---|---|
GITHUB_TOKEN |
Access to authorized target repos |
GROQ_API_KEY |
LLM provider key (when LLM_PROVIDER=groq) |
LLM_MODEL |
Model id (see .env.example) |
Add a scope file under scopes/ listing allowed_repos before auditing a new target. Defaults ship for this repo (scopes/spectre.yaml) and a demo sample (scopes/vuln-sample.yaml).
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]" && npm install && cp .env.example .env
# Terminal 1
python -m spectre.cli serve
# Terminal 2
npm run dev # http://localhost:5173Use SPECTRE only on authorized repositories. Keep tokens in .env; never commit secrets or unredacted findings. Report vulnerabilities in SPECTRE privately to the maintainers.