Add ClusterFuzzLite fuzzing integration

[malsomesh9]

Summary

• add ClusterFuzzLite project configuration, Docker build integration, and PR fuzzing workflow
• add standalone Atheris fuzz targets for transaction deserialization, entity ID parsing, key parsing, and contract function parameter ABI encoding
• add continuous fuzzer build artifacts on pushes to main

Details

This follows the ClusterFuzzLite Python integration pattern:

• .clusterfuzzlite/project.yaml declares language: python
• .clusterfuzzlite/Dockerfile uses gcr.io/oss-fuzz-base/base-builder-python
• .clusterfuzzlite/build.sh generates protobufs, installs the SDK, installs Atheris/PyInstaller, and packages each *_fuzzer.py target into $OUT
• .github/workflows/clusterfuzzlite.yml runs PR fuzzing in code-change mode and uploads continuous builds on pushes to main

Fixes #2143

Validation

• /tmp/hiero-sdk-python-venv/bin/python -m ruff check .clusterfuzzlite/*.py
• /tmp/hiero-sdk-python-venv/bin/python -m ruff format --check .clusterfuzzlite/*.py
• /tmp/hiero-sdk-python-venv/bin/python -m compileall -q .clusterfuzzlite
• bash -n .clusterfuzzlite/build.sh
• ruby -e 'require "yaml"; YAML.load_file(".github/workflows/clusterfuzzlite.yml"); YAML.load_file(".clusterfuzzlite/project.yaml")'
• local smoke import/execution of each fuzzer TestOneInput with an Atheris API stub
• /tmp/hiero-sdk-python-venv/bin/python -m pytest tests/fuzz -q
• /tmp/hiero-sdk-python-venv/bin/pre-commit run --files .clusterfuzzlite/project.yaml .clusterfuzzlite/Dockerfile .clusterfuzzlite/build.sh .clusterfuzzlite/transaction_from_bytes_fuzzer.py .clusterfuzzlite/entity_id_fuzzer.py .clusterfuzzlite/keys_fuzzer.py .clusterfuzzlite/contract_params_fuzzer.py .github/workflows/clusterfuzzlite.yml

Notes

Docker is not available on the local host, so the ClusterFuzzLite container build was not run locally. Installing Atheris directly on this macOS Python 3.14 environment also fails because Apple Clang does not provide libFuzzer; the workflow uses ClusterFuzzLite's Linux base-builder image, which is the intended execution environment.

[coderabbitai]

Warning

Rate limit exceeded

@malsomesh9 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 33 minutes and 49 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 33 minutes and 49 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: cb0e1da7-c0ab-43c3-94af-b35ddef08a9d

📥 Commits

Reviewing files that changed from the base of the PR and between 15032e1 and bc59969.

📒 Files selected for processing (8)

• .clusterfuzzlite/Dockerfile
• .clusterfuzzlite/build.sh
• .clusterfuzzlite/contract_params_fuzzer.py
• .clusterfuzzlite/entity_id_fuzzer.py
• .clusterfuzzlite/keys_fuzzer.py
• .clusterfuzzlite/project.yaml
• .clusterfuzzlite/transaction_from_bytes_fuzzer.py
• .github/workflows/clusterfuzzlite.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 29 complexity

Metric	Results
Complexity	29

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[github-actions]

Hi there! I'm the LinkedIssueBot.
This pull request has been automatically closed due to the following reason(s):

• Reason: You are not assigned to the linked issue. Please ensure you are assigned before reopening the pull request.
  Please read - Creating Issues - How To Link Issues Workflow

Thank you,
From Python SDK team