For vulnerabilities in the supported NSB release, avoid disclosing exploit details in a public issue. Contact the repository owner privately, or use GitHub's Report a vulnerability option under the repository Security tab if private vulnerability reporting is enabled. Include the affected NSB version, environment, reproduction steps and likely impact.
For non-sensitive bugs, scientific inaccuracies, or documentation problems, open a regular GitHub issue. Do not include private observatory datasets, credentials or restricted catalogue data in public reports.
The latest released version receives priority for security fixes. Scientific model-validity concerns are distinct from software-security issues and should be documented with the affected domain and reproducible evidence.