The table below indicates which versions of JAINet currently receive security updates.

If you discover a potential security vulnerability in JAINet, please do not open a public GitHub issue.

Instead, report the issue privately to the project maintainer.

When reporting a vulnerability, please include:

• A clear description of the issue.
• Steps to reproduce the problem.
• The affected version of JAINet.
• Any proof-of-concept code (if available).
• Suggested mitigation (optional).

Every report will be reviewed as quickly as possible.

If the issue is confirmed, a fix will be prepared and released in a future version.

Security reports may include, but are not limited to:

• Code execution vulnerabilities.
• Unsafe deserialization.
• Dependency vulnerabilities.
• Data leakage.
• Unsafe file handling.
• Authentication or authorization issues (future modules).
• Insecure model loading.
• Malicious dataset handling.

Please allow reasonable time for investigation and remediation before publicly disclosing a security issue.

Responsible disclosure helps protect all JAINet users.

JAINet aims to follow secure software engineering practices, including:

• Secure dependency management.
• Static type checking.
• Continuous testing.
• Input validation.
• Safe handling of medical datasets.
• Reproducible builds.
• Transparent security updates.

Thank you for helping improve the security of JAINet.