If you discover a security vulnerability in Polysome, please report it responsibly:
Please do not open a public GitHub issue for security vulnerabilities.
Instead, please report security issues via email to:
Include in your report:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: We will acknowledge receipt of your vulnerability report within 48 hours
- Updates: We will provide regular updates on the status of the issue
- Fix Timeline: We aim to release a fix within 30 days for critical issues
- Credit: With your permission, we will credit you in the fix announcement
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
- Model Files: Only load models from trusted sources
- User Input: Validate and sanitize any user-provided data before processing
- Environment Variables: Keep sensitive environment variables (API keys, paths) secure
- Docker: Use appropriate security contexts when running Docker containers
- Data Privacy: Be mindful of data privacy when processing sensitive information with LLMs
- Keep Dependencies Updated: Regularly update Polysome and its dependencies
- Access Control: Limit file system access to necessary directories only
- Resource Limits: Set appropriate resource limits when running workflows
- Audit Logs: Review logs for any suspicious activity
- Network Security: When using remote models or APIs, use secure connections
- This framework executes user-provided workflow configurations - ensure workflows are from trusted sources
- LLM outputs should be validated before use in production systems
- File system operations require appropriate permissions
Security updates will be published as new releases. Subscribe to repository notifications to stay informed.