BugTraceAI is a modular web pentesting suite with independently deployable products, published models and integrations. Contributions to code, documentation, reproducible bug reports and usability are welcome.
| Area | Repository |
|---|---|
| Suite documentation and architecture | BugTraceAI |
| Web-scanning engine, terminal workspace, REST and MCP | BugTraceAI-CLI |
| Browser workspace, analyst tools, AIrepeater and ModelLab | BugTraceAI-WEB |
| Independent API-target engine | BugTraceAI-API |
| Installation, updates and service management | BugTraceAI-Launcher |
| Practice application and planted challenges | BugStore |
| ReconFTW MCP integration | reconftw-mcp |
For feedback on a published checkpoint, use the corresponding model's Community tab in the BugTraceAI model catalog.
- Read the selected repository's README and development instructions.
- For a substantial feature or architecture change, discuss the proposal in an issue before implementation.
- Fork that repository and create a branch for a focused change.
- Update the relevant documentation and add or run checks appropriate to the change.
- Open a pull request describing the problem, the resulting behavior and the verification performed.
Keep code, comments, commit messages and public documentation in English. Follow the conventions of the repository you are changing.
Use the relevant repository's issue templates. Include the affected component and version, setup method, reproduction steps, and expected and observed behavior. Use a practice target for examples and redact credentials and sensitive target data.
For installation and usage questions, see SUPPORT.md.
Report vulnerabilities in BugTraceAI privately according to the repository's security policy or the organization reporting guide.
Contributions follow the license of the repository receiving them. Published models have their own model cards and license terms; consult those cards before contributing or redistributing model artifacts.