Security and privacy safeguards are maintained on the current main branch. The repository preserves a historical research experiment and does not provide a deployed service or supported clinical system.

Report concerns that could expose or enable access to:

• participant-level source or derived data;
• credentials, tokens, private keys, or provider access material;
• restricted data-dictionary content;
• record-level notebook exports or generated artifacts;
• a repository configuration that could publish ignored sensitive files.

Also report dependency or workflow vulnerabilities when they affect the dataset-free validation path. General model-quality, methodological, and documentation questions may use the public issue templates when they contain no sensitive information.

Do not disclose a suspected data exposure in a public issue, pull request, discussion, screenshot, or copied log. Contact the public security maintainer, Fatemeh Sabourinia, through the private contact options available on that GitHub profile. Share the minimum information needed to locate the problem and do not attach participant data.

The maintainer will assess the report, limit further exposure, preserve appropriate evidence without copying sensitive records, and coordinate any provider or platform notification that may be required. Response timing depends on severity and access to the affected system.

A security report is not a route for obtaining the dataset, model access, clinical advice, or individual predictions. Dataset access remains controlled by the official provider.