PAGES
← all tools
◆ AI-Powered Offensive Security

RAPTOR

v3.1.0 open-source

RAPTOR chains static analysis, binary analysis, LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. vulnerability validation, exploit generation, and patch writing into one autonomous security research workflow.

Summary

RAPTOR is an open-source autonomous agent framework for offensive/defensive research, licensed under MIT. It functions as a framework, not a distinct tool, and is written in Python, utilizing Claude Code for its core logic. It is intended for researchers interested in vulnerability discovery and exploit generation, and it sits in the space generally occupied by other code analysis tools, as evidenced by its connection to CodeQL. The project's authorship list includes multiple named contributors, and it maintains active integration through GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. for code scanning.

RAPTOR chains static analysis, binary analysis, LLM vulnerability validation, exploit generation, and patch writing into one autonomous security research workflow.

How RAPTOR helps

Which functions in this codebase are actually reachable and worth an attacker's time?

traces call paths and framework entry points across languages, marking sinks the code path can actually reach versus dead-code matches a plain grep would flag

Is this static-analysis hit a real bug or noise?

replays the finding through LLM-driven validation and exploit generation, producing a working trigger or a discarded verdict rather than a bare line number

Can this vulnerability be turned into a working exploit?

drives an end-to-end chain from the confirmed finding through exploit generation and patch writing, so the output is a proof rather than a hypothesis

Do the bugs only visible after macro expansion actually exist in this C/C++ codebase?

re-runs the rule set over the preprocessor-expanded translation units, catching matches that scanning the raw source misses

Does this container image or tarball carry a dependency with a known exploited vulnerability?

runs the supply-chain composition pipeline directly against the image or archive and gates on severity or known-exploited status rather than requiring a checked-out source tree

all 13 features, with the evidence for each →

Languages

Not documented

Features

13 capabilities · 3 backed by code, an API document or a real run

Built from RAPTOR's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • RAPTOR covers 1 of the 5 supply chain security capabilities we track.
  • RAPTOR covers 1 of the 2 vulnerability management capabilities we track.

What RAPTOR offers you

  • Command-line interface2
  • Scripting language support2
  • CI/CD pipeline integration1
  • Python scripting support1
All capabilities 13 capabilities
Static analysis shipped Runs static analysis on a codebase and maintains a local cache of Semgrep rules used during scanning. 12 releases · 8 other sources · first seen Apr 2026

Also counts toward: CI/CD pipeline integration, Command-line interface, Python scripting support

release 12 total

  • Adds --compiler-scan-max-tus <n> flag to cap the number of translation units analyzed by --compiler-scan (default 2000). v3.1.0 · Sep 2026 · source · release history
  • Adds --audit-verbose flag for strace-style verbose output during sandbox audit runs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v3.1.0 · Sep 2026 · source · release history
  • Adds --expanded-semgrep flag to re-run Semgrep rules over preprocessor-expanded views of macro-heavy C/C++ translation units. v3.1.0 · Sep 2026 · source · release history
  • Adds OCI registry, Dockerfile, and tar as scan substrates, enabling RAPTOR to analyze container images and tarballs directly. v3.1.0 · Sep 2026 · source · release history
  • Introduces corpus runner, rule evaluation, and label linter v3.1.0 · Sep 2026 · source · release history
  • Adds --compiler-scan / --no-compiler-scan flags to enable or disable a compiler-analyzer channel using gcc -fanalyzer or clang --analyze. v3.1.0 · Sep 2026 · source · release history

docs

  • - [uv](https://docs.astral.sh/uv/) for Python dependency management, Python 3.12+, and Node.js 18+. - Semgrep (uv tool install semgrep) for static analysis. CodeQL is optional but recommended. seen Oct 2026 · source
  • text Authors: Gadi Evron, Daniel Cuthbert, Thomas Dullien (Halvar Flake), Michael Bargury, John Cartwright ([@gadievron](https://github.com/gadievron), [@danielcuthbert](https://github.com/danielcuthbert), [@thomasdullien](https://github.com/thomasdullien), [@mbrg](https://github.com/mbrg),… docs update · Sep 2026 · source

example

  • Scan a macro-heavy C/C++ codebase and catch bugs that only appear in expanded preprocessor output, which plain Semgrep misses. /scan /path/to/c-project --expanded-semgrep --languages c,cpp v3.1.0 · Sep 2026 · source
  • Run the compiler-analyzer channel on a C/C++ codebase alongside Semgrep, capping the number of translation units to keep the scan tractable on a large repo. /scan /path/to/c-project --compiler-scan --compiler-scan-max-tus 500 --build-command 'make -j4' v3.1.0 · Sep 2026 · source
  • Run a standalone CodeQL analysis with Z3 SMT constraint solving for deep dataflow tracing. python3 raptor.py /codeql <path> v3.0.0 · Apr 2026 · source
  • Update local Semgrep rule pack cache python3 engine/semgrep/tools/cache-packs.py update
  • Update local Semgrep rule cache python3 engine/semgrep/tools/cache-packs.py update
  • Run static analysis on a codebase /scan /path/to/code
Software composition analysis shipped Scans dependencies for known advisories and supports severity and KEV-based gating to filter results. 2 releases · 7 other sources · first seen Sep 2026

Shared capability: Dependency scanning

release

  • Adds a corpus runner with rule evaluation and label linting for calibrating detection rules. v3.1.0 · Sep 2026 · source · release history
  • Adds a full SCA (software composition analysis) mechanical pipeline with supply-chain detector and first-party hardening. v3.1.0 · Sep 2026 · source · release history

example 7 total

  • Check specific package for advisories python3 raptor.py sca check PyPI django 4.2.10
  • Auto-fix vulnerable dependencies python3 raptor.py sca --repo /path/to/project fix
  • Run software composition analysis on project python3 raptor.py sca --repo /path/to/project
  • SCA with severity and KEV failure gates python3 raptor.py sca --repo /path/to/project --fail-on-severity high --fail-on-kev
  • SCA scan with severity and KEV gating python3 raptor.py sca --repo /path/to/project --fail-on-severity high --fail-on-kev
  • Check specific package version for vulnerabilities python3 raptor.py sca check PyPI django 4.2.10
Autonomous vulnerability research and exploit generation verified Chains static analysis, binary analysis, and LLM-powered validation to autonomously research vulnerabilities and generate exploits for offensive and defensive purposes. 2 releases · 5 other sources · first seen Sep 2026

release

  • Enables Mantle and InvokeModel coexistence for LLM provider support v3.1.0 · Sep 2026 · source · release history
  • Adds full multi-LLM provider support for the analysis dispatch layer, with Mantle and InvokeModel coexistence. v3.1.0 · Sep 2026 · source · release history

docs

  • - Claude Code with an active subscription (Max, Pro, Team, or Enterprise) or an Anthropic API key. This is the orchestration layer for the interactive raptor shell -- optional if you only need the standalone CLIs, see [Running fully standalone](#running-fully-standalone-no-claude-code) below. docs update · Sep 2026 · source
  • Autonomous offensive/defensive cyber research framework chaining static analysis, binary analysis, LLM-powered vulnerability validation, exploit generation, and
  • Autonomous offensive/defensive cyber research framework that chains static analysis, binary analysis, LLM-powered vulnerability validation, exploit generation,

command line

  • up — Re-provision a recorded environment spec (CVE or DESC- id) and leave it running; prints the endpoint (isolated-network container address, or a loopback port with --allow-egress) as the test target for exploit/PoC work v3.1.0 · Sep 2026 · command-line history

example

  • Full autonomous scan and validation pipeline /agentic /path/to/code
Framework-specific reachability analysis shipped Detects framework APIs and sinks with support for JavaScript and Go function-as-argument registration. 4 releases · first seen Sep 2026

Shared capability: Reachability analysis

Also counts toward: Scripting language support

release

  • Adds JS and Go function-as-argument framework registration for reachability analysis. v3.1.0 · Sep 2026 · source · release history
  • Adds JS/Go function-as-argument framework registration in reachability v3.1.0 · Sep 2026 · source · release history
  • Adds mechanical sink discovery and framework API detection in understand v3.1.0 · Sep 2026 · source · release history
  • Adds mechanical sink discovery and framework API detection (MAP-5f) to the understand module. v3.1.0 · Sep 2026 · source · release history
Automated suppression validation verified Verifies and scores suppression records against expected findings to prevent false negatives. 2 releases · 1 other source · first seen Sep 2026

release

  • Adds per-function annotations emitted across validation stages A, B, and D via the validate module. v3.1.0 · Sep 2026 · source · release history
  • Adds inventory sanitizer-cut suppressor v3.1.0 · Sep 2026 · source · release history

command line

  • warm — score suppression records as would-suppress counts (raw numbers unchanged) v3.1.0 · Sep 2026 · command-line history
CVE environment modeling verified Creates and manages isolated environments to replicate CVE-specific conditions for reproducible vulnerability research. 2 releases · 1 other source · first seen Sep 2026

Also counts toward: Command-line interface

release

  • Adds cve-env as an integrated package (packages/cve_env) for CVE environment modeling (Phase 1). v3.1.0 · Sep 2026 · source · release history
  • Integrates cve-env as packages/cve_env (Phase 1 lift-and-shift) v3.1.0 · Sep 2026 · source · release history

command line

  • up — Re-provision a recorded environment spec (CVE or DESC- id) and leave it running; prints the endpoint (isolated-network container address, or a loopback port with --allow-egress) as the test target for exploit/PoC work v3.1.0 · Sep 2026 · command-line history
Dynamic sandbox auditing shipped Executes targets in an isolated sandbox to trace system calls and network behavior for runtime analysis. 2 releases · 1 other source · first seen Sep 2026

release

  • Adds --audit-budget <n> flag to cap the maximum number of audit events collected per run. v3.1.0 · Sep 2026 · source · release history
  • Adds sandbox --audit mode for bulk auditing workflows v3.1.0 · Sep 2026 · source · release history

example

  • Audit a target's sandbox behavior before enforcing — log every syscall that would have been blocked without actually blocking anything, with a cap to avoid log flooding. /scan /path/to/target --audit --audit-verbose --audit-budget 500 v3.1.0 · Sep 2026 · source
Web application analysis shipped Analyzes web applications using a correlation tier with poisoned-render oracles and framework registration support. 3 releases · first seen Sep 2026

Also counts toward: Scripting language support

release

  • Adds JS and Go function-as-argument framework registration for reachability analysis. v3.1.0 · Sep 2026 · source · release history
  • Adds bare-host correlation tier for web expectations, check legs, and poisoned-render oracle v3.1.0 · Sep 2026 · source · release history
  • Adds a web correlation tier with expectations, check legs, and a poisoned-render oracle for web vulnerability analysis. v3.1.0 · Sep 2026 · source · release history
Agentic detection engineering shipped Automatically generates custom security checkers based on confirmed findings to improve future detection capabilities. 2 releases · first seen Sep 2026

release

  • Adds agentic checker synthesis — the system now generates a checker per confirmed finding. v3.1.0 · Sep 2026 · source · release history
  • Synthesises checker per confirmed finding via agentic KNighter follow-up v3.1.0 · Sep 2026 · source · release history
Binary analysis shipped Investigates binaries with evidence-backed findings to support vulnerability research. 1 release · 1 other source · first seen Sep 2026

release

  • Adds leaf analysis modules from the audit branch to the analysis subsystem v3.1.0 · Sep 2026 · source · release history

example

  • Evidence-backed binary investigation /binary investigate /path/to/binary
Frida evidence integration shipped Incorporates Frida-based instrumentation to capture runtime execution traces for evidence-backed analysis. 2 releases · first seen Sep 2026

release

  • Adds Frida evidence pipeline with full consumer wiring and reachability integration. v3.1.0 · Sep 2026 · source · release history
  • Introduces frida evidence pipeline with full consumer wiring and reachability integration v3.1.0 · Sep 2026 · source · release history
Source intelligence gathering shipped Gathers source-level intelligence using specialized substrates and minimal rules for initial assessment. 2 releases · first seen Sep 2026

release

  • Adds source intelligence substrate with a minimal axis-1 rule for source-level intel gathering. v3.1.0 · Sep 2026 · source · release history
  • Adds source_intel substrate with axis 1 minimal rule v3.1.0 · Sep 2026 · source · release history
Supply-chain security scanning shipped Provides specialized analysis for container images, tarballs, and OCI registries to detect vulnerabilities in packaged dependencies. 2 releases · first seen Sep 2026

release

  • Adds OCI registry, Dockerfile, and tar as scan substrates, enabling RAPTOR to analyze container images and tarballs directly. v3.1.0 · Sep 2026 · source · release history
  • Adds OCI registry + Dockerfile + tar substrate support in core v3.1.0 · Sep 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for RAPTOR, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail RAPTOR puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Coverage

Missing something? Tell us

What RAPTOR connects to, runs on and detects, read from its release notes and docs. So far: 6 new integrations, 2 new detections, 1 new supported platform.

Show

9 changes, tracked since Oct 8, 2026.

  • Oct 82026

    new Custom Semgrep rules for Python, Go, Java, JS/TS

    Covers 18: SQLi, XSS, SSRF, SSTI, command injection, deserialisation and 12 more

    Semgrep (~150 rules) — taint-tracking and pattern rules for Python, Go, Java, and JS/TS. Covers SQLi, XSS, SSRF, SSTI, command injection, deserialisation, XXE, LDAP/NoSQL injection, path traversal, open redirect, log/header injection, eval injection, ReDoS, prototype pollution, JWT misconfiguration, weak crypto, insecure TLS, and hardcoded secrets.

    The source lists 150. Counted here as one change.

    Source ↗

  • Oct 82026

    new Custom Coccinelle rules for C/C++ memory safety and integer bugs

    Adds double free, use-after-free, free of non-base pointer, free of stack array, mmap'd memory, use-after-close, sign extension, double sizeof. 8 in all.

    Coccinelle (68 rules) — structural matching for C/C++. Memory safety (double free, use-after-free, free of non-base pointer, free of stack array, mmap'd memory, use-after-close), integer bugs (overflow, sign extension, double sizeof), resource leaks (popen/fclose

    The source lists 68. Counted here as one change.

    Source ↗

  • Oct 82026

    new Semgrep registry pack offline cache tool

    With p/security-audit, p/owasp-top-ten

    For registry packs (p/security-audit p/owasp-top-ten, etc.), the cache directory ships empty. A cache tool (engine/semgrep/tools/cache-packs.py) handles population

    Source ↗

  • Oct 82026

    new Ghidra RE bridge integration

    With .gpr

    /ghidra Ghidra RE bridge: attach/import .gpr projects, cross-version diff, findings export Beta

    Source ↗

  • Oct 82026

    new Frida dynamic instrumentation integration

    /frida Dynamic instrumentation via Frida Alpha

    Source ↗

  • Oct 82026

    new ffuf and nuclei integration for web scanning

    /web Web application scanning: crawl, ffuf/nuclei integration, oracle-verified injection, blind SSRF callbacks Beta

    Source ↗

How we count

Read from 1 of 8 release notes and docs updates we hold for RAPTOR. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through RAPTOR's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

8 entries

  1. October 20261
  2. September 20266
  3. April 20261
    Show
    Coverage in all entries

    8 entries

    Project health

    Issue, contributor and maintainer activity in gadievron/raptor, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 33 +33 vs prior 12 months
    2. Maintainers 1 +5 joined · −4 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog not measured open issues today
    1. Issues opened / month not measured
    2. Open backlog not measured
    3. Contributors / month 3
    4. Commits / month 2,728
    5. Stars not measured
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →