phanpy/SECURITY.md

40 wiersze
1.6 KiB
Markdown
Czysty Zwykły widok Historia

2025-04-21 09:49:08 +00:00
# Security Policy
## Supported Versions
Only the **latest production release** of Phanpy receives security updates. Always update to the newest production version for the best protection.
## Reporting a Vulnerability
**Please dont discuss security issues in public GitHub issues.** Instead:
1. **GitHub Private Reporting** (preferred):
- Click ["Report a vulnerability"](https://github.com/cheeaun/phanpy/security/advisories/new) under the **Security** tab.
2. **Email**:
- Reach out to me directly at cheeaun@gmail.com
**Include**:
- Steps to reproduce the issue
- Which parts of Phanpy are affected
- How severe you think the impact could be
## Disclosure Policy
**Heads up:** Im a solo maintainer working on Phanpy in my free time. While I take security seriously, I cant promise enterprise-grade response times. Heres how Ill handle reports:
1. **Confirmation**: Ill acknowledge reports when possible, but this might take weeks due to limited availability.
2. **Fixing**: Critical bugs will be prioritized, but fixes may take significant time. If its urgent, feel free to follow up.
3. **Public Disclosure**: Patched vulnerabilities will be disclosed once the fix is confirmed stable and most users have updated.
## Security Practices
### For Users
- Use Phanpy with a Mastodon instance that enforces **HTTPS**.
- Treat OAuth tokens like passwords – dont share them!
### For Developers
- **Dependencies**: GitHub Dependabot alerts are enabled for vulnerability monitoring.
- **Code**:
- Basic input sanitization to prevent XSS.
- *Planned*: Improvements to client-side storage security (contributions welcome!).