Scope
Public Mirogate websites, public Mirogate open-source repositories, and public pages under mirogate.com are in scope for private vulnerability reports.
Security
Responsible disclosure for Mirogate systems.
If you believe you found a vulnerability in a Mirogate public website, open-source project, or related public system, report it privately with enough detail to reproduce and verify the issue.
Report Format
Send practical evidence, not public posts.
- Use the subject line:
Security Report for Mirogate. - Send the report to [email protected].
- Include the affected URL, repository, or system name.
- Describe the impact and the steps needed to reproduce the issue.
- Include screenshots, request samples, or logs when useful.
- Do not publish exploit details before Mirogate has had time to investigate.
Out of scope
Social engineering, spam, denial-of-service attempts, physical attacks, and automated scans without a concrete vulnerability are not useful reports.
Safe handling
Test only what is necessary, avoid accessing data that is not yours, and stop immediately if testing could affect availability or privacy.
Open Source
Project security policies
Mirogate open-source repositories include security notes and are linked from the public open-source hub.