-
Notifications
You must be signed in to change notification settings - Fork 78
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Use Case
Why is this Rust workflow needed?
E.g., automating cargo-fuzz, detecting dependency vulnerabilities with cargo-audit, enforcing Clippy rules, or preventing unsafe code patterns.
Proposed Solution
How should this workflow work in FuzzForge?
- Fuzzing: Preconfigured
cargo-fuzz, sanitizer builds, regression corpora. - SAST:
cargo-auditagainst RustSec DB, Clippy linting, unsafe code checks. - Combined: One Rust Security workflow that runs fuzzing + SAST in CI.
Alternatives
Other approaches you considered (e.g., manual GitHub Actions setup, third-party CI tools, manual runs).
Implementation
(Optional) Technical details like YAML snippets, Docker setup, or using cargo-deny.
Category
- 🛠 Workflow Automation
- 🔗 Fuzzer Integration
- 🔍 SAST / Static Analysis
Additional Context
Links:
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request