# baarai/artex

> ARTEX is a self-hosted penetration testing platform that security testers use to run LLM-driven tests against a target. A planner splits a goal into intents, workers run real tools to carry them out, and the results are written into two linked graphs, one describing the target and one describing how the test is progressing. The core is written in Go, with a Next.js user interface embedded in the same binary and PostgreSQL for storage.

Source: https://github.com/baarai/artex
Indexed: commit 705ac80 on 2026-11-20 by Repowise. Facts come from the source and git history, not from the maintainer.

## Facts

- Type: App
- Language: Go
- Stars: 14,991 at index time
- License: AGPL-3.0
- Code health: 6.1/10, Fair
- Last commit: 2026-11-20
- Contributors: 33

## Install

From the README: https://github.com/baarai/artex#installation

Clone the artex repository.
    git clone https://github.com/baarai/artex.git

Move into the artex folder.
    cd artex

Copy the example environment file to .env, then set POSTGRES_PASSWORD in it.
    cp .env.example .env

Build the image from your checkout and start ARTEX with PostgreSQL.
    docker compose up -d --build

Print the one-time setup token that the /setup page asks for on the first visit.
    docker compose logs artex | grep "Setup token"

## How it works

The command cmd/artex/main.go starts the program, and server/server.go sets up HTTP routing, JWT authentication and server-sent events, with a Manager that owns tasks, engines and database stores. For each task, an engine runs a planner loop alongside worker goroutines that claim intents and execute them. The agent directory builds each agent's tools and prompt, and agent/tools.go exposes the two graphs to the language model as tools it can call. The db package, including db/exploration.go, reads and writes the PostgreSQL records for tasks, assets, findings and model settings. The evidence package stores captured traffic through its Store type, so a finding can point to the request and response that prove it. Outbound HTTP requests from the server, agent, enrich and traffic packages pass through the egress package, which controls their pacing and route.

- cmd/artex-archive-check/main.go: entry point
- cmd/artex/main.go: entry point
- server/server.go: entry point
- .github/scripts/bot.sh: central file
- .github/workflows/bot.yml: central file
Modules: web, server, db, agent, intercept, traffic, notify, scripts. 875 files, 188,060 lines, 8,506 symbols.

## Code health

- Score: 6.1/10 (Fair)
- Trend: 6.2 on 2026-11-18, 6.1 on 2026-11-20
- Rank: #195 of 4,000+ indexed repos
- Hotspots: web/src/app/(main)/function/tasks/page.tsx, server/server.go, web/src/app/(main)/function/tasks/detail/_tabs/sessions-tab.tsx, db/exploration.go, agent/tools.go
- Lowest file: intercept/argv_compound.go
- Dead code: 186 findings

## Maintenance

- Last commit 2026-11-20, first commit 2026-07-26, 765 commits
- 33 contributors, bus factor 2

## Security

- Security findings are shown to signed-in users at https://repowise.dev/repo/baarai/artex/security

## More

- Page: https://repowise.dev/repo/baarai/artex
- Ask this codebase: https://repowise.dev/repo/baarai/artex/chat
- Docs: https://repowise.dev/repo/baarai/artex/docs
- MCP (signs in with Repowise on first use):
    claude mcp add --transport http repowise https://api.repowise.dev/mcp/baarai/artex
