Community Driven Plugin Ecosystem for OWTF

OWTF right now has a fixed set of plugins. If a security researcher wants to add a new tool or technique, there is no way to do it without touching the core codebase. Plugins also run inside the main OWTF process, which means one bad plugin can crash the whole system. There is no isolation, no sandboxing and no way for the community to contribute plugins. I am planning to fix this by building a simple plugin ecosystem. First, an upload API where users can submit a .py file with metadata. Before saving, a validator checks the code and blocks unsafe things like eval, exec, file writes or socket access. Safe plugins get stored with a pending review status. Second, sandboxed execution. I will run each plugin in an isolated process with limits on CPU, memory, and time and plug this into the existing plugin manager so it works seamlessly. Third, plugin discovery. I will add a /plugins endpoint and a small marketplace UI where users can browse, filter, install and run approved plugins easily. Deliverables: PluginValidator module, SandboxRunner module, UserPlugin database model and migration, upload and listing API endpoints, Plugin Marketplace UI with browse and upload pages, Nuclei plugin as reference implementation, unit and integration tests and a plugin authoring guide.