Skip to content

Latest commit

 

History

History
17 lines (9 loc) · 1.09 KB

SECURITY.md

File metadata and controls

17 lines (9 loc) · 1.09 KB

Security Policy

Supported version

Security and integrity fixes are applied to the latest public release and the default branch.

Reporting software vulnerabilities

Do not post credentials, exploitable private-system details, or confidential laboratory data in a public Issue. Use GitHub private vulnerability reporting when enabled for the repository. For non-sensitive reproducible defects, open a standard Issue with the affected version and minimal reproduction.

Scientific integrity issues

Incorrect labels, provenance errors, unsafe overclaims, applicability-domain bypasses, or mismatched Python/JavaScript inference should be reported with the artifact version, input record, expected behavior, and supporting evidence. These reports may be handled publicly when they contain no restricted information.

Chemistry safety boundary

ChemPredict does not provide operational safety approval. Outputs must not be used to determine reagent quantities, scale-up, cyanide handling, ventilation, quenching, or waste procedures. Follow institutional SOPs and qualified supervision for all experiments.