Files
fuzzforge_ai/.github/ISSUE_TEMPLATE/workflow_submission.md
tduhamel42 40d48a8045 feat: Complete Temporal migration cleanup and fixes
- Remove obsolete docker_logs.py module and container diagnostics from SDK
- Fix security_assessment workflow metadata (vertical: rust -> python)
- Remove all Prefect references from documentation
- Add SDK exception handling test suite
- Clean up old test artifacts
2025-10-14 15:02:52 +02:00

2.4 KiB

name, about, title, labels, assignees
name about title labels assignees
🔄 Workflow Submission Contribute a security workflow or module to the FuzzForge community [WORKFLOW] workflow, community

Workflow Name

Provide a short, descriptive name for your workflow.

Description

Explain what this workflow does and what security problems it solves.

Category

What type of security workflow is this?

  • 🛡️ Security Assessment - Static analysis, vulnerability scanning
  • 🔍 Secret Detection - Credential and secret scanning
  • 🎯 Fuzzing - Dynamic testing and fuzz testing
  • 🔄 Reverse Engineering - Binary analysis and decompilation
  • 🌐 Infrastructure Security - Container, cloud, network security
  • 🔒 Penetration Testing - Offensive security testing
  • 📋 Other - Please describe

Files

Please attach or provide links to your workflow files:

  • workflow.py - Main Temporal flow implementation
  • Dockerfile - Container definition
  • metadata.yaml - Workflow metadata
  • Test files or examples
  • Documentation

Testing

How did you test this workflow? Please describe:

  • Test targets used: (e.g., vulnerable_app, custom test cases)
  • Expected outputs: (e.g., SARIF format, specific vulnerabilities detected)
  • Validation results: (e.g., X vulnerabilities found, Y false positives)

SARIF Compliance

  • My workflow outputs results in SARIF format
  • Results include severity levels and descriptions
  • Code flow information is provided where applicable

Security Guidelines

  • This workflow focuses on defensive security purposes only
  • I have not included any malicious tools or capabilities
  • All secrets/credentials are parameterized (no hardcoded values)
  • I have followed responsible disclosure practices

Registry Integration

Have you updated the workflow registry?

  • Added import statement to backend/toolbox/workflows/registry.py
  • Added registry entry with proper metadata
  • Tested workflow registration and deployment

Additional Notes

Anything else the maintainers should know about this workflow?


🚀 Thank you for contributing to FuzzForge! Your workflow will help the security community automate and scale their testing efforts.

💬 Questions? Join our Discord Community to discuss your contribution!