Only the latest stable release of NTX-RPC is actively supported with security updates.

If you discover a security vulnerability in NTX-RPC, please do not create a public issue.

Instead, use GitHub's Private Vulnerability Reporting feature to report the issue privately.

Please include:

• A description of the vulnerability
• Steps to reproduce the issue
• Screenshots or logs (if applicable)
• Potential impact
• Suggested mitigation or fix (optional)

This policy applies to:

• NTX-RPC desktop application
• Discord Rich Presence integration
• Configuration files
• Update system (if applicable)
• Project source code
• GitHub Actions workflows

The following are generally not considered security vulnerabilities:

• Visual/UI bugs
• Application crashes without a security impact
• Feature requests
• Performance issues
• Third-party service outages

After receiving a report:

1. The issue will be reviewed and validated.
2. A fix will be developed if necessary.
3. A patched release will be published.
4. The reporter may be credited unless they request otherwise.

Please allow reasonable time for vulnerabilities to be investigated and fixed before publicly disclosing any details.

Thank you for helping improve the security of NTX-RPC.