How devdanzin/fusil works
Project type and purpose
• Type: Open-source Python fuzzing framework with a plugin-style “fusil-…” fuzzer CLI layer.
• Purpose: Provide a library (fusil/) of multi-agent system components and probes to launch, monitor, and score fuzzing sessions against arbitrary target programs. It ships with ready-to-run fuzzers in fuzzers/.
File structure
• Top-level directories:
• fusil/: core Python library implementing application setup, multi-agent system (MAS), probes (process, network, file, syslog, CPU), manglers, session management, logging, utilities.
• fuzzers/: small executable wrappers (“fusil-foo”) invoking fusil library against a specific target.
• doc/: Sphinx sources describing architecture, configuration, components, how-tos.
• tests/: unit and integration tests for command-line parsing, file-watch, help outputs, etc.
• Configuration/build files: setup.py, setup.cfg, MANIFEST.in for packaging; .gitignore; doc/Makefile.
Insights from README
• Fusil creates isolated session directories, limits resources, redirects output, and launches probes.
• Architecture: multi-agent system where agents (process agent, network agent, mangle agent, logger agent, etc.) cooperate via mailboxes.
• CLI fuzzers call fusil.application to configure and start sessions.
Detailed guidance
• How configuration flows from CLI → Config → Application → Agents.