Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Enhance testing by adding fuzzing

Open
  • Is something wrong?
#981 0 comments 1 reaction 1 assignee View on GitHub

Maintainers usually reply within 1 day

@MacOS is already working on this.

Since Aug 13, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement

This issue is under active development and will be updated periodically based on the discussion below.

🧠 D: DOCUMENT — Problem & Opportunity

Currently, SKaiNET misses out an opportunity to systematically test it's functionality, and discover vulnerabilities, because it does not use fuzzing. This does matter for SKaiNET because it processes large amounts of data and is hence highly vulnerable for attacks. This issue proposes to add fuzzing.

Summary (1–2 sentences):

This issue aims to add fuzzing to it's tests.

🔍 A: ASSESS — Feasibility & Impact

Provide an evaluation of the proposal. Address the following:

✔️ Feasibility

Adding fuzzing to the tests is not straightforward to add because we have to settle on a third party library first, and then decide which parts of SKaiNET we want to test with fuzzing..

There are no architectural constraints because the issue pertains to tests.

✔️ Expected Impact

Adding fuzzing does neither - what it does, however, increase the probility of finding bugs.

✔️ Risks / Constraints

Neither of the three - we are not changing the library.

✔️ Dependencies

Adding fuzzing relies on a SKaINET module and requires a third-party library. We have to settle on both before we start.

📚 R: RESEARCH — What Must Be Understood First?

Document research tasks or open questions that must be answered before implementation:

Literature

MallisseryWu2023.pdf
ManèsEtAl2021.pdf
MillerEtAl1990.pdf
ZhaoZhang2018.pdf
ZhuEtAl2022.pdf

Research Tasks
  • Review existing frameworks (PyTorch, JAX, TensorFlow, etc.)
  • Identify relevant algorithms or formulas
  • Compare design patterns for modularity
  • Investigate numerically stable or optimized variants
  • Check for relevant academic papers or benchmarks
Open Questions

List unknowns that contributors should discuss or resolve.

  • Which module do we want to fuzzy test?
  • Which third-party library to we want to use for fuzzing?

🛠️ C: CODE — Implementation Plan

Break down actionable steps required to deliver this feature:

Development Tasks
  • Design module interface
  • Implement core functionality
  • Write unit tests (correctness + edge cases)
  • Add configuration integration
  • Update training loop or pipeline components (if applicable)
  • Add documentation & examples
  • Create or update benchmarks (optional)
  • Submit PR referencing this issue
Acceptance Criteria
  • Feature works as intended and passes all tests
  • Fully documented with clear examples
  • Follows SKaiNET coding style & modular design
  • Reviewed and approved by maintainers
  • No regressions introduced elsewhere

💬 Additional Notes

Add diagrams, pseudo-code, references, or implementation notes that may help future contributors.

Dominant language
Kotlin
Stars
52
Forks
15
Avg merge
1d 15h
Merged PRs (30d)
36

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SKaiNET-developers/SKaiNET

All issues in SKaiNET-developers/SKaiNET

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.