CheckOps
Radamsa
Radamsa is an MIT-licensed, scriptable test-case generator for robustness testing that mutates sample files into malformed inputs.
Latest public signals
Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.
Introduction
Radamsa is a test case generator for robustness testing, a fuzzer. Its README says it is typically used to test how well a program withstands malformed and potentially malicious inputs, by reading sample files of valid data and generating interestingly different outputs.
Selling points are that it has found many bugs in programs that matter, is easily scriptable, and is easy to get running. It is black-box: no instrumentation, just a command that writes mutated inputs to files, stdout or a network socket, so any program in any language can be tested.
The project is hosted on GitLab under the MIT licence, with commits as recent as February 2026.
Saving every crashing input with its seed makes failures reproducible and easy to turn into regression tests.
Features
- Sample-based mutation: Starts from valid files.
- Black-box: No instrumentation needed.
- Scriptable: Simple CLI.
- Many outputs: Files, stdout or TCP.
- Seeds: Reproducible runs.
- Any target: Language-agnostic.
Pros
- Free to use: Open source under MIT.
- Simplicity: One command to start.
Cons
- No coverage guidance: Less efficient than coverage-guided fuzzers.
- Harness DIY: You script the loop.
- Small community: Fewer updates.
Usage and Links (Example)
echo "HAL 9000" | radamsa
radamsa -n 100 -o fuzz-%n.json samples/*.json
for f in fuzz-*.json; do ./parser "$f" || echo "crash: $f"; done
Resources:
Pricing
Radamsa is free and open source under the MIT licence.
Recommended for?
- Testers fuzzing black-box programs quickly.
Conclusion
Radamsa is the quickest way to throw malformed data at anything.
Pair it with coverage-guided fuzzing for depth.
On CheckOps, Radamsa is filed under the Security testing stage. Related tools listed here include libFuzzer, AFL++, honggfuzz, LibAFL, OSS-Fuzz and ClusterFuzzLite. A short trial on a real project, with your own code, data and pipeline, is usually the fastest way to choose between them, because fit matters more than feature lists. Facts here come from the official site, documentation and repository, checked on 11 November 2026.
Alternatives
Other tools on CheckOps that cover similar ground. Open a page, or compare one with Radamsa side by side.
LlibFuzzerlibFuzzer is LLVM's in-process, coverage-guided, evolutionary fuzzing engine, built into Clang via -fsanitize=fuzzer and used with sanitizers to find memory-safety and logic bugs in C and C++.Compare with Radamsa
AAFL++AFL++ is the community-maintained successor to Google's AFL: a coverage-guided fuzzer with faster execution, better mutations and instrumentation, custom mutators and modes for binaries, licensed AGPL-3.0-or-later.Compare with Radamsa
Hhonggfuzzhonggfuzz is Google's Apache-2.0 security-oriented fuzzer with evolutionary, feedback-driven fuzzing based on software and hardware code coverage.Compare with Radamsa
LLibAFLLibAFL is a Rust library of reusable fuzzer components from the AFL++ team, for building fast, scalable, custom fuzzers across platforms and targets.Compare with Radamsa
OOSS-FuzzOSS-Fuzz is Google's free continuous fuzzing service for critical open-source projects, running libFuzzer, AFL++ and other engines at scale on ClusterFuzz.Compare with Radamsa
CClusterFuzzLiteClusterFuzzLite is Google's Apache-2.0 continuous fuzzing solution that runs in CI such as GitHub Actions, fuzzing pull requests and running batch fuzzing with coverage reports.Compare with Radamsa