As the sole developer of the Pokémon 3D API, I prioritize the security of the project and its users. If you discover any security-related issues or vulnerabilities, please follow the steps below to report them responsibly.
If you discover a security vulnerability in the Pokémon 3D API, please report it to me directly. Do not disclose the vulnerability publicly until it has been addressed.
-
Create an Issue on GitHub
- Go to the Issues page of the Pokémon 3D API repository.
- Create a new issue and include the following details:
- A detailed description of the vulnerability.
- Steps to reproduce the issue (if applicable).
- Any relevant files, logs, or screenshots to help us investigate the issue.
-
Contact Us on Discord
- For quicker collaboration, join our Discord Server and message me directly. My username is sudhanshu30072006. Please label your message as a security report. Once the issue is reported, I will prioritize it and work on a fix as soon as possible.
- We will review the report and acknowledge it within 48 hours.
- I will work on fixing the issue as quickly as possible.
- Once a fix is implemented and deployed, I will update the repository and notify the reporter.
If the issue requires further discussion or if there are questions regarding the security report, we will set up a GitHub Discussion to collaborate and resolve the issue. You can find or create discussions here: GitHub Discussions.
The master branch of the Pokémon 3D API is the only version supported with security updates. Other versions, releases, or tags will not be supported with security patches.
| Version | Supported |
|---|---|
master |
✅ |
| Any other version/release/tag | ❌ |
Only the master branch will receive security updates. Other versions, releases, or tags will not be supported with security patches.
I sincerely appreciate all security contributions and responsible disclosures. Your help keeps the Pokémon 3D API project secure and improves the experience for everyone.
Thank you for your support!