← Project README · Code of Conduct · Contributing

This policy covers security issues involving the repository's scripts, dependencies, build tools, CI workflows, automation, and configuration.

It does not cover factual, mathematical, technical, or typographical errors in the study materials. See Content errors below.

Security fixes are handled for the current default branch.

Older commits, archived artifacts, and historical releases are not maintained as separate supported versions.

If you discover a security vulnerability, do not open a public issue containing technical details.

Report it privately through GitHub Private Vulnerability Reporting.

Please include, when possible:

Use sanitized examples. Do not include real credentials, access tokens, personal information, or unrelated sensitive data.

If GitHub Private Vulnerability Reporting is unavailable, open a public issue requesting a private reporting channel without disclosing vulnerability details.

After receiving a report, the maintainer will review the issue, attempt to reproduce it, and coordinate a fix and disclosure when appropriate.

Please do not disclose the vulnerability publicly until a fix is available or disclosure has been coordinated.

Reporters may be credited in a security advisory or release notes when appropriate unless they request anonymity.

The notes in this repository are unofficial, student-created material and may contain errors, omissions, outdated information, or inaccurate AI-assisted content.

These are not security vulnerabilities unless they create an actual security risk.

For incorrect notes, broken links, documentation problems, or PDF compilation and rendering issues, use the relevant public issue form or open a Pull Request. Include a reliable source when appropriate.