Do not open a public issue for a suspected vulnerability, exposed credential, private identifier, or unsafe deployment detail.

Use GitHub's private vulnerability-reporting feature when it is available. Otherwise, contact the maintainer through the private contact method listed on the GitHub profile.

Include the affected file or component, reproduction conditions, expected impact, and any recommended mitigation. Do not include live credentials, private addresses, personal data, or exploit material in public evidence.

Security fixes target the current default branch. Historical releases and archived repositories are preserved for portfolio context and are not guaranteed to receive fixes.