RAPTOR
v3.1.0 open-sourceThe section your link pointed to isn't on RAPTOR's page any more, so we've brought you to the top.
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.
raptor --project myapp --max-cost-usd 5 /agentic /path/to/target raptor /analyze findings.sarif export _RAPTOR_TRUSTED=1 export OLLAMA_HOST=http://localhost:11434 python3 raptor.py agentic --repo /path/to/code export _RAPTOR_TRUSTED=1 libexec/raptor-project-manager create myapp --target /path/to/code libexec/raptor-project-manager use myapp python3 raptor.py agentic --repo /path/to/code libexec/raptor-project-manager findings python3 raptor.py agentic --repo /path/to/code export _RAPTOR_TRUSTED=1 libexec/raptor-project-manager create myapp --target /path/to/code libexec/raptor-project-manager use myapp python3 raptor.py agentic --repo /path/to/code raptor /path/to/target --project myapp --threat-model --max-cost-usd 20 docker build -f .devcontainer/Dockerfile -t raptor:latest . && docker run --rm -it -v "$(pwd):/workspaces/raptor" -v "/path/to/target-folder:/workspaces/target" raptor:latest raptor raptor /path/to/target --project my-audit # Then inside the session: /agentic --codeql --threat-model --max-cost-usd 15 docker run --privileged \ -v "$(pwd):/workspaces/raptor" \ -v "/path/to/target-folder:/workspaces/target" \ raptor:latest /scan /path/to/target --audit --audit-verbose --audit-budget 500 /scan /path/to/c-project --compiler-scan --compiler-scan-max-tus 500 --build-command 'make -j4' /scan /path/to/c-project --expanded-semgrep --languages c,cpp /scan /path/to/target --audit --audit-verbose --audit-budget 500 /scan /path/to/c-project --compiler-scan --compiler-scan-max-tus 500 --build-command 'make -j4' /scan /path/to/c-project --expanded-semgrep --languages c,cpp python3 raptor.py /codeql <path>
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
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
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.
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.
-
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.
-
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
-
Oct 82026
new Ghidra RE bridge integration
With .gpr
/ghidra Ghidra RE bridge: attach/import .gpr projects, cross-version diff, findings export Beta
-
Oct 82026
new Frida dynamic instrumentation integration
/frida Dynamic instrumentation via Frida Alpha
-
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
-
Oct 82026
new CVE data source integration for fix-commit discovery
With /cve-diff, OSV, NVD, GitHub, GitLab
/cve-diff Discover and diff the fix commit for a CVE across OSV, NVD, GitHub, and GitLab Beta
-
Oct 82026
new AFL++ binary fuzzing integration
/fuzz Binary fuzzing with AFL++ and crash analysis Stable
-
Oct 82026
new VS Code devcontainer support
With .devcontainer/devcontainer.json
VS Code devcontainers are also supported. To mount a target folder, add it to the mounts section of .devcontainer/devcontainer.json
Vulnerability & code scanning 7
Source control & CI/CD 2
Other 6
Containers & orchestration 1
Nothing first seen in this window. That doesn't mean RAPTOR shipped nothing, only that we found no record of it.
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
8 entries
No entries match these filters.
- October 20261
- September 20266
- April 20261
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.
- Contributors 33 +33 vs prior 12 months
- Maintainers 1 +5 joined · −4 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 3
- Commits / month 2,728
- Stars 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.