trailofbits / trailofbits/ruzzy
Fuzzing candidates
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 120
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
- https://github.com/msgpack/msgpack-ruby
- https://github.com/flori/json
- https://github.com/ruby/psych (YAML)
- https://github.com/cabo/cbor-ruby
- https://github.com/mongodb/bson-ruby
- https://github.com/ruby/date
- https://github.com/ruby/zlib
EDIT: more:
- https://github.com/puma/puma/tree/master/ext/puma_http11
- https://github.com/k0kubun/hamlit
- https://github.com/jgarber/redcloth
- https://github.com/ruby/strscan
- https://github.com/ruby/etc
- https://github.com/ruby/openssl/blob/master/ext/openssl/ossl_asn1.c
- https://github.com/ruby/openssl/blob/master/ext/openssl/ossl_config.c
- https://github.com/kgiszczak/tomlib
- https://github.com/jm/toml
- https://github.com/emancu/toml-rb
- https://github.com/fluent/fluentd
- https://github.com/slim-template/slim
- https://github.com/ruby/rbs
- https://github.com/protocolbuffers/protobuf/tree/main/ruby
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the listed Ruby projects and identify their parsing or extension entry points, beginning with the repositories linked in the issue. Determine which candidates are compatible with ruzzy and define what a usable fuzzing target and reproducible setup would be for each selected project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100