Welcome Contributors!
RAPTOR is in alpha and welcomes contributions from anyone, on anything. Whether you’re fixing bugs, adding features, improving documentation, or sharing ideas, we appreciate your help.Community-driven: What will make RAPTOR truly transformative is community contributions. It’s open source, modular, and extensible.
Quick Start for Contributors
What to Contribute
Bug Fixes
Found a bug? Fix it!
- Check existing issues
- Create issue if new
- Submit fix with tests
New Features
Ideas for improvements:
- Better web exploitation
- YARA signature generation
- Port to Cursor/Windsurf
- New scan capabilities
Documentation
Help improve docs:
- Fix typos
- Add examples
- Clarify instructions
- Write tutorials
Testing
Improve test coverage:
- Add test cases
- Test edge cases
- Report test failures
- Add vulnerable samples
Integrations
Connect RAPTOR to tools:
- CI/CD platforms
- Security scanners
- Bug trackers
- Notification systems
Skills & Personas
Contribute expertise:
- New expert personas
- Custom skills
- Analysis techniques
- Exploit methods
Development Setup
Project Structure
Key Components
Python Execution Layer
Python Execution Layer
Core scripts:
raptor.py- Unified launcher, routes to modesraptor_agentic.py- Full autonomous workflowraptor_fuzzing.py- Binary fuzzing orchestrationraptor_codeql.py- CodeQL database and analysis
- Adding new command-line arguments
- Changing workflow orchestration
- Adding new modes
Packages
Packages
9 security capabilities:
llm_analysis- LLM-based vulnerability analysisstatic-analysis- Semgrep integrationcodeql- CodeQL semantic analysisfuzzing- AFL++ binary fuzzingweb- Web application testing (alpha)exploit_feasibility- Binary exploit analysisexploitability_validation- Validation pipelinebinary_analysis- Binary utilitiesoss_forensics- GitHub forensics
- Adding new analysis capabilities
- Improving existing algorithms
- Adding new tools integration
Claude Code Integration
Claude Code Integration
.claude/ directory:CLAUDE.md- Bootstrap instructions (always loaded)commands/*.md- Slash command definitionsagents/*.md- Autonomous agent definitionsskills/- Reusable skills and techniques
- Adding new slash commands
- Creating new agents
- Adding expert personas
- Creating custom skills
Test Suite
Test Suite
test/ directory:comprehensive_test.sh- Full test suiteintegration_tests.sh- Tool integration teststest_workflows.sh- Workflow validationdata/- Vulnerable code samples
- Adding new test cases
- Adding vulnerable samples
- Testing new features
Pull Request Guidelines
Before Submitting
1. Run Tests
1. Run Tests
Ensure all tests pass:
All tests should pass before submitting PR.
2. Code Quality
2. Code Quality
Follow Python best practices:Style guidelines:
- Use clear variable names
- Add docstrings for functions
- Comment complex logic
- Follow PEP 8 (loosely)
3. Documentation
3. Documentation
Update documentation:
- Add docstrings to new functions
- Update README.md if adding features
- Add examples for new commands
- Update ARCHITECTURE.md for major changes
4. Commit Messages
4. Commit Messages
Use clear, descriptive commit messages:Format:Types:
Add:New featureFix:Bug fixUpdate:Enhancement to existing featureRefactor:Code restructuringDocs:Documentation onlyTest:Test additions/fixes
PR Template
Adding New Features
Adding a New Package
Adding a New Command
Adding an Expert Persona
Code Review Process
Development Resources
Architecture Guide
Understand RAPTOR’s technical architecture
Extending Launcher
How to add new capabilities
Testing Guide
Test suite documentation
Dependencies
External tools and licenses
Community
Communication Channels
Slack Community
Join #raptor channel on Prompt||GTFO Slack:https://join.slack.com/t/promptgtfo/shared_invite/zt-3kbaqgq2p-O8MAvwU1SPc10KjwJ8MN2wGreat for:
- Questions about development
- Discussing new features
- Getting help with contributions
- Sharing ideas
GitHub Issues
Use for:
- Bug reports
- Feature requests
- Documentation issues
- Security vulnerabilities
Contribution Ideas
Looking for something to work on? Here are some ideas:Easy (Good First Issues)
Easy (Good First Issues)
- Fix typos in documentation
- Add more test cases
- Improve error messages
- Add usage examples
- Update dependencies
Medium
Medium
- Add new Semgrep rules
- Improve web exploitation module
- Add new expert personas
- Create custom skills
- Improve test coverage
- Add integration with bug trackers
Hard
Hard
- Port to Cursor/Windsurf/Copilot
- YARA signature generation
- Advanced exploit techniques
- Machine learning for prioritization
- Distributed fuzzing
- Custom CodeQL queries
Fun Ideas
Fun Ideas
- Hacker poetry generator
- ASCII art raptor animations
- Custom reporting templates
- Integration with security conferences (CTF scoreboard)
- Gamification of security research
Recognition
We appreciate all contributions! Contributors are: ✅ Listed in commit history ✅ Mentioned in release notes ✅ Credited in documentation ✅ Part of the RAPTOR community Current contributors:- Gadi Evron (@gadievron)
- Daniel Cuthbert (@danielcuthbert)
- Thomas Dullien / Halvar Flake (@thomasdullien)
- Michael Bargury (@mbrg)
- John Cartwright (@grokjc)
- YOU? 🦖
License
By contributing to RAPTOR, you agree that your contributions will be licensed under the MIT License. RAPTOR License:- MIT License
- Copyright (c) 2025 Gadi Evron, Daniel Cuthbert, Thomas Dullien (Halvar Flake), Michael Bargury
- Retain your copyright
- Licensed under MIT (same as RAPTOR)
- Can be used, modified, distributed freely
Questions?
Slack
Ask on #raptor channel
GitHub Issues
Open an issue
Thank You!
We appreciate you!
Thank you for contributing to RAPTOR. Together, we’re building an autonomous security research framework that will transform how we find and fix vulnerabilities.Get them bugs! 🦖