This document describes the security procedures and policies for maatify/common. We take the security of our ecosystem seriously, and we appreciate any responsible disclosure that helps keep our libraries, users, and integrations safe.
If you discover a security vulnerability, please DO NOT open a public issue.
Instead, contact us directly via the secure channels:
- Email (Preferred): security@maatify.dev
- Backup Email: mohamed@maatify.dev
- PGP Key (optional): Available upon request
When reporting a vulnerability, please include:
- A clear description of the issue
- Steps to reproduce
- Affected versions or components
- Potential impact
- Possible mitigation ideas (if any)
We aim to acknowledge all reports within 48 hours.
Only the latest major/minor versions receive security updates.
| Version | Status |
|---|---|
| 1.x | π’ Active security support |
| 0.x (legacy) | π΄ No longer supported |
If you depend on an unsupported version, please upgrade as soon as possible.
We classify security issues using four levels:
| Level | Description |
|---|---|
| Critical | Allows remote code execution, credential leaks, or severe data exposure |
| High | Authentication bypass, privilege escalation, or data corruption |
| Medium | Information disclosure, insufficient validation, partial denial-of-service |
| Low | Minor bugs with limited or no practical impact |
Once a vulnerability is reported:
- Initial review β We investigate and confirm the issue.
- Internal tracking β The issue is logged privately.
- Patch development β A secure fix is prepared and tested.
- Coordinated release β A patched version is published.
- Disclosure β A security advisory (GHSA) is published on GitHub, if applicable.
We do not reveal reporter identity unless explicitly permitted.
To keep your integration secure:
- Always use the latest stable version of the library.
- Never expose
.envfiles or configuration data. - Use secure DSNs with strong passwords.
- Follow PSR-12 and Maatify best practices for token handling.
- Validate and sanitize all user input before passing to your app.
- Review your CI/CD configuration for secret leaks.
We fully support and encourage responsible vulnerability disclosure. If you follow the guidelines above, you will always receive fair, respectful, and prompt communication from the maintainers.
- Do not perform tests that violate applicable laws.
- Do not perform actions that could disrupt production services.
- Do not access data that does not belong to you.
π§© maatify/common β Core Utilities, DTOs & Standards for the Maatify Ecosystem
Β© 2025 Maatify.dev β’ Maintained by Mohamed Abdulalim (@megyptm)
Β© 2025 Maatify.dev
Engineered by Mohamed Abdulalim (@megyptm) β https://www.maatify.dev
π Full documentation & source code:
https://github.com/Maatify/common
Built with β€οΈ by Maatify.dev β Unified Ecosystem for Modern PHP Libraries