[PR #1] [MERGED] [WIP] Add single raptor launcher for main process

## 📋 Pull Request Information **Original PR:** https://github.com/gadievron/raptor/pull/1 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 11/16/2025 **Status:** ✅ Merged **Merged:** 11/16/2025 **Merged by:** [@danielcuthbert](https://github.com/danielcuthbert) **Base:** `main` ← **Head:** `copilot/add-single-raptor-launcher` --- ### 📝 Commits (3) - [`25c6f12`](https://github.com/gadievron/raptor/commit/25c6f12f966970e7162f6fe21825fb24927970f0) Initial plan - [`c97feeb`](https://github.com/gadievron/raptor/commit/c97feeb6fa5c4ffe2abbe4c4e4a135549f6139ec) Add unified RAPTOR launcher with ASCII dinosaur banner - [`4b538a1`](https://github.com/gadievron/raptor/commit/4b538a1ac85114122fe2e8b92a90bf892776061a) Add comprehensive documentation for extending the unified launcher ### 📊 Changes **4 files changed** (+863 additions, -40 deletions) <details> <summary>View changed files</summary> 📝 `.gitignore` (+3 -0) 📝 `README.md` (+132 -40) ➕ `docs/EXTENDING_LAUNCHER.md` (+391 -0) ➕ `raptor.py` (+337 -0) </details> ### 📄 Description ## Unified RAPTOR Launcher Implementation - Complete - [x] Create `raptor.py` - unified launcher with ASCII raptor banner - [x] Add command routing for all engines: - [x] Static analysis (Semgrep) - [x] CodeQL analysis - [x] Fuzzing (AFL++) - [x] Full agentic workflow - [x] Web scanning - [x] LLM analysis - [x] Implement subcommand architecture using argparse - [x] Add help system showing all available modes - [x] Update .gitignore to exclude output directory - [x] Update README with new launcher instructions - [x] Test the launcher with different modes - [x] Add comprehensive documentation on extending with new engines (docs/EXTENDING_LAUNCHER.md) ## Summary Successfully implemented a unified launcher (`raptor.py`) that serves as a single entry point for all RAPTOR security testing capabilities. Key features: ### Features ✅ **Single Entry Point**: `python3 raptor.py <mode>` for all operations ✅ **ASCII Raptor Banner**: Eye-catching dinosaur banner on every launch ✅ **Mode Routing**: Supports scan, fuzz, web, agentic, codeql, and analyze modes ✅ **Help System**: Context-sensitive help with `raptor.py help <mode>` ✅ **Easy Extension**: Simple pattern to add new engines/scanners ✅ **Backward Compatible**: All original scripts (raptor_agentic.py, etc.) still work ### Testing All tests pass: - Help display ✓ - Invalid mode detection ✓ - Mode delegation ✓ - ASCII banner ✓ - Argument forwarding ✓ ### Documentation - Updated README.md with unified launcher examples - Created docs/EXTENDING_LAUNCHER.md with complete guide for adding new engines - Updated architecture diagram in README ### User Experience Users can now run: ```bash python3 raptor.py agentic --repo /path/to/code python3 raptor.py scan --repo /path/to/code python3 raptor.py fuzz --binary /path/to/binary ``` Instead of having to remember individual script paths. Adding new engines is now trivial - just add a mode handler function and register it.  <details> <summary>Original prompt</summary> > We need a single raptor launcher than users can call, as the main root process of the whole project. this means when we add new engines or scanners, we can just feed it into that and not ask the user to run individual commands each time. > > Please understand all the code and come up with the best way to implement this. </details>  --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem commented

2026-03-02 04:07:52 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/gadievron/raptor/pull/1
Author: @Copilot
Created: 11/16/2025
Status: ✅ Merged
Merged: 11/16/2025
Merged by: @danielcuthbert

Base: main ← Head: copilot/add-single-raptor-launcher

📝 Commits (3)

25c6f12 Initial plan
c97feeb Add unified RAPTOR launcher with ASCII dinosaur banner
4b538a1 Add comprehensive documentation for extending the unified launcher

📊 Changes

4 files changed (+863 additions, -40 deletions)

View changed files

📝 .gitignore (+3 -0)
📝 README.md (+132 -40)
➕ docs/EXTENDING_LAUNCHER.md (+391 -0)
➕ raptor.py (+337 -0)

📄 Description

Unified RAPTOR Launcher Implementation - Complete

Create raptor.py - unified launcher with ASCII raptor banner
Add command routing for all engines:
- Static analysis (Semgrep)
- CodeQL analysis
- Fuzzing (AFL++)
- Full agentic workflow
- Web scanning
- LLM analysis
Implement subcommand architecture using argparse
Add help system showing all available modes
Update .gitignore to exclude output directory
Update README with new launcher instructions
Test the launcher with different modes
Add comprehensive documentation on extending with new engines (docs/EXTENDING_LAUNCHER.md)

Summary

Successfully implemented a unified launcher (raptor.py) that serves as a single entry point for all RAPTOR security testing capabilities. Key features:

Features

✅ Single Entry Point: python3 raptor.py <mode> for all operations
✅ ASCII Raptor Banner: Eye-catching dinosaur banner on every launch
✅ Mode Routing: Supports scan, fuzz, web, agentic, codeql, and analyze modes
✅ Help System: Context-sensitive help with raptor.py help <mode>
✅ Easy Extension: Simple pattern to add new engines/scanners
✅ Backward Compatible: All original scripts (raptor_agentic.py, etc.) still work

Testing

All tests pass:

Help display ✓
Invalid mode detection ✓
Mode delegation ✓
ASCII banner ✓
Argument forwarding ✓

Documentation

Updated README.md with unified launcher examples
Created docs/EXTENDING_LAUNCHER.md with complete guide for adding new engines
Updated architecture diagram in README

User Experience

Users can now run:

python3 raptor.py agentic --repo /path/to/code
python3 raptor.py scan --repo /path/to/code
python3 raptor.py fuzz --binary /path/to/binary

Instead of having to remember individual script paths. Adding new engines is now trivial - just add a mode handler function and register it.

Original prompt

We need a single raptor launcher than users can call, as the main root process of the whole project. this means when we add new engines or scanners, we can just feed it into that and not ask the user to run individual commands each time.

Please understand all the code and come up with the best way to implement this.

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}