#1414th of 19 in Security

t3mp3st

Multi-agent offensive-security framework driven by your coding agent or local model

Stars
7k
License
AGPL-3.0
Last commit
Sep 2026
Last release
Sep 2026
Language
TypeScript
Stars, last 19 weeks+7,013
30 Jun 2026: 2 stars7 Jul 2026: 3,399 stars14 Jul 2026: 4,646 stars21 Jul 2026: 5,001 stars28 Jul 2026: 5,202 stars4 Aug 2026: 5,343 stars11 Aug 2026: 5,461 stars18 Aug 2026: 5,539 stars25 Aug 2026: 5,611 stars1 Sept 2026: 5,854 stars8 Sept 2026: 6,000 stars15 Sept 2026: 6,092 stars22 Sept 2026: 6,177 stars29 Sept 2026: 6,243 stars6 Oct 2026: 6,388 stars13 Oct 2026: 6,481 stars20 Oct 2026: 6,553 stars27 Oct 2026: 6,614 stars3 Nov 2026: 6,668 stars10 Nov 2026: 7,015 stars

2 on 30 Jun 20267,015 on 10 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

T3MP3ST runs a recon, exploit and report kill chain against authorized targets from a browser War Room or CLI. It uses a connected local coding agent (Claude Code, Codex, Hermes, OpenCode, Oh My Pi), an API key, or an offline model via Ollama or an OpenAI-compatible server. Its benchmark claims (XBEN 90.1% pass@1, Cybench 23/40) come from a single-agent loop and recompute with `npm run verify-claims`.

Who it is for: Security researchers running authorized pentests, CTFs and vulnerability hunts

Strengths

  • Benchmark numbers re-derive from committed data with `npm run verify-claims`
  • Works keyless via a signed-in local coding agent or an offline model
  • Egress-scope containment is on by default and refuses off-target public hosts
  • Status table separates stable, experimental and planned components

Weaknesses

  • Multi-operator swarm exploitation is unbenchmarked and described as unreliable
  • Cloud, mobile, AD and binary domains are scaffolding only
  • Raw benchmark transcripts are stripped, so only graded verdicts can be re-checked
  • AGPL-3.0 license limits use in closed network services

What it needs

  • GPU optional
  • Docker + Compose
  • Needs Node.js/npm, git, Docker (optional), Ollama or OpenAI-compatible server (optional)
  • Models: Claude Code, Codex, Hermes, OpenCode, Oh My Pi
  • port 3333

Quick answers

Is t3mp3st open source?

Yes. Its code is on GitHub under the AGPL-3.0 license.

Can you run t3mp3st with Docker?

Yes. Its repository has a Docker setup: a Dockerfile, a Compose file or a published image.

Does t3mp3st need a GPU?

No. It runs on a CPU and can use a GPU when you have one.

Also in Security

See all 19
Also in Security
RankProjectScore
1shannonAutonomous pentester that exploits web apps and APIs using source analysis51.7k stars+3,096 (+6.4%) in 30 daysAGPL-3.091 out of 100
2ifixaiPython CLI that audits AI agents for policy, access and reliability failures44.8k stars+22,029 (+97%) in 30 daysApache-2.087 out of 100
3StrixAutonomous AI pentesting agents that validate vulnerabilities with working exploits75k stars+7,196 (+11%) in 30 daysApache-2.084 out of 100
#4pentagiAutonomous multi-agent penetration testing system with sandboxed security tools33.9k stars+8,543 (+34%) in 30 daysMIT77 out of 100
#5ai-infra-guardRed-teaming platform for AI infra CVEs, MCP servers, agent skills and jailbreaks7.5k starsApache-2.075 out of 100