Magayaga takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub profiles and private organizations, which include Magayaga.
Please do not report security vulnerabilities through public GitHub issues.
If you prefer to submit without logging in, send email to cyrilmagayaga@proton.me or cjmagayaga957@gmail.com.
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
Use this section to tell people about which versions of your project are currently being supported with security updates.
| Version | Supported | Notes |
|---|---|---|
name1 or name_1 |
✅ Corrected | This is codename or App name, not a real name |
1_name or 1name |
❌ Unacceptable | |
v1.0 or v1, and r75 |
✅ Corrected | This is version, remainder version or codename, not a real or last name |
v.1.0, 1v, r.75, 75r, or 1.0.v |
❌ Unacceptable |
Use this section to tell people how to report a vulnerability.
Tell them where to go, how often they can expect to get an update on a reported vulnerability, what to expect if the vulnerability is accepted or declined, etc.
We prefer all communications to be in English.
Copyright (c) 2023-2026 Cyril John Magayaga. All rights reserved.
Licensed under the MIT license.