4,203
stars
1,881
forks
17
watchers
178
prs
67
issues
4
releases
README
ARTEX Autonomous penetration testing that keeps its receipts. (upstream: Autumn-27/ARTEX, AGPL-3.0) Self-hosted multi-agent offensive security. A planner explores, workers run real tools, and every finding stays bound to the assets and HTTP traffic that prove it. Quick start · Screenshots · How it works · Install · Configuration · Security --- ARTEX is a self-hosted, LLM-driven penetration testing platform. It is not a chat wrapper around a scanner: a planner splits a goal into intents, workers execute them with real tools, and the results are written back into two linked graphs: one for what you know about the target, one for how the test is progressing. Every finding can carry the captured request and response that justify it, and every autonomous action passes through scope rules, approval gates and budgets. - It explores, it doesn't chat. Goal decomposition, intent dispatch, worker execution and write-back form a closed loop that keeps advancing until the goal is proven. - Two graphs, one audit trail. The shared asset graph says what exists; the per-task exploration graph says what was tried, what it produced, and why. Anchors link the two. - Findings with evidence. A recording MITM proxy and a browser extension capture real traffic; findings, evidence quotes and retests are tied to the exact request/response. - Autonomy with brakes. Human-in-the-loop approvals, argv-prefix rules, scope/deny gates, token and turn budgets, a target noise governor, and prompt-injection framing on tool output. - Self-hosted and model-agnostic. One Go binary with the Next.js UI embedded, PostgreSQL, your own Anthropic/OpenAI-compatible endpoint, or a local Ollama. --- Quick start bash git clone https://github.com/BaaRai/ARTEX.git cd ARTEX cp .env.example .env set POSTGRES_PASSWORD (and optionally an LLM key) docker compose up -d --build builds from this checkout, starts PostgreSQL Open http://localhost:8787. On the first visit /setup asks for the one-time setup token printed at startup: bash docker compose logs artex | grep "Setup token" There is no prebuilt Docker image to pull: the image is always built from your checkout. For all installation paths (script, binaries, source, release archives), see Installation. --- Screenshots | Tasks | Findings | | :---: | :---: | | !Tasks | !Findings | | Task execution: sessions and tool calls | Exploration graph | | :---: | :---: | | !Execution | !Exploration graph | | Asset coverage graph | Traffic recording | | :---: | :---: | | !Asset coverage graph | !Traffic | | Human-in-the-loop chat | Interception approvals | | :---: | :---: | | !Chat | !Interception | More screenshots (assets, agents, LLM, logs) | Assets | Agent management | | :---: | :---: | | !Assets | !Agent | | LLM configuration | Backend logs | | :---: | :---: | | !LLM | !Logs | --- How it works Dual-graph architecture: exploration graph + asset graph ARTEX separates what the goals are from h
Top issues
#154[Feature Request] Support custom User-Agent and fixed full API endpoint URL5 comments · 2026-11-08#129DemonRoute as a provider option via ARTEX_LLM_BASE_URL4 comments · 2026-10-31#242UI concept: simulated operator console for autonomous pentest runs1 comments · 2026-11-15#89Benchmark: diversify public ground truth beyond Juice Shop (XBOW set is saturated; Cybench/CyberGym candidates)1 comments · 2026-10-12#124Adversarial audit: map the 2026 agentic attack classes (memory poisoning, plan hijacking, tool abuse) onto ARTEX itself0 comments · 2026-10-22#5OpenClaw-style chat bot: drive ARTEX from Telegram (inbound bridge + remote approvals)0 comments · 2026-10-09
Latest release
v0.6.0 v0.6.0 2026-11-11Summary ARTEX v0.6.0 makes a finding provable, hardens the agents against the content they read, and adds an opt-in approval gate for targets. The target gate ships OFF by default and through the API only, so existing deployments keep their current behavior after upgrading. Full list: CHANGELOG.md · compare v0.5.1...v0.6.0 Highlights - Verified findings (S1): findings carry a POE level and a verification status. verified requires a bound proof or verification response, a declared POE level of 3 or more, and every evidence quote of 8 runes or more found verbatim in a bound body. A retest v