# Security Policy
## Supported Versions
| 0.1.x | :white_check_mark: |
## Reporting a Vulnerability
We take the security of Instafy seriously. If you have discovered a security vulnerability, please report it to us privately.
### How to Report
**Please do not report security vulnerabilities through public GitHub issues.**
Instead, please send an email to: **security@example.com** (replace with your actual security contact)
Please include the following information in your report:
- Type of vulnerability
- Full description of the vulnerability
- Steps to reproduce the issue
- Potential impact
- Any possible mitigations you've identified
### What to Expect
- **Acknowledgment**: We will acknowledge receipt of your vulnerability report within 48 hours.
- **Assessment**: We will assess the vulnerability and determine its impact and severity within 7 days.
- **Fix**: We will work on a fix and keep you informed of our progress.
- **Disclosure**: Once a fix is available, we will:
1. Release a patched version
2. Publish a security advisory
3. Credit you for the discovery (unless you prefer to remain anonymous)
### Security Update Process
1. Security issues are fixed in private
2. A new version is released with the fix
3. A security advisory is published
4. Users are notified through GitHub releases and the project README
## Security Best Practices
When using Instafy:
- Keep your installation up to date
- Only process images from trusted sources
- Be cautious when processing images from untrusted or unknown sources
- Use appropriate file permissions for input and output directories
- Review logs for any suspicious activity when processing images
## Known Security Considerations
### Image Processing
- Large images may consume significant memory
- Malformed images could potentially cause crashes
- File system permissions should be properly configured
### Dependencies
We regularly update dependencies to include security patches. Run `cargo audit` to check for known vulnerabilities in dependencies.
## Security-Related Configuration
### Logging
- Avoid logging sensitive file paths in production
- Use appropriate log levels (`RUST_LOG` environment variable)
- Sanitize file paths in logs if processing sensitive data
### File System
- Ensure proper permissions on output directories
- Validate input directory paths
- Be cautious with user-supplied paths
## Vulnerability Disclosure Policy
- We will acknowledge your contribution in our security advisory
- We follow responsible disclosure practices
- We aim to fix critical vulnerabilities within 30 days
- We will coordinate with you on the disclosure timeline
## Bug Bounty
We currently do not have a bug bounty program, but we greatly appreciate security research and responsible disclosure.
## Contact
For security issues: **security@example.com**
For general questions: [Open an issue](https://github.com/yourusername/instafy/issues)
## Past Security Advisories
No security advisories have been published yet.
---
Last updated: 2025-10-11