gloo.foo is currently in active development. We provide security updates for:
| Version | Supported |
|---|---|
| main | ✅ |
| < 1.0 | ❌ |
We take security seriously. If you discover a security vulnerability in gloo.foo, please report it responsibly:
- Do not create a public GitHub issue for security vulnerabilities
- Email security reports to: [email protected]
- Include as much detail as possible:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: We'll acknowledge receipt within 24 hours
- Assessment: We'll assess the vulnerability within 5 business days
- Updates: We'll provide regular updates on our progress
- Resolution: We aim to resolve critical vulnerabilities within 30 days
gloo.foo processes user input and executes commands. Key security areas include:
- Input Validation: All user input is validated before processing
- Context Cancellation: All operations respect context cancellation to prevent resource exhaustion
- Memory Safety: Streaming processing prevents memory exhaustion attacks
- Command Injection: Commands are isolated and don't execute arbitrary shell commands
We follow responsible disclosure practices:
- We'll work with you to understand and validate the issue
- We'll develop and test a fix
- We'll coordinate the disclosure timeline with you
- We'll publicly acknowledge your contribution (unless you prefer to remain anonymous)
When contributing to gloo.foo:
- Always validate user input
- Use context cancellation for long-running operations
- Prefer streaming over loading entire files into memory
- Follow the principle of least privilege
- Don't execute arbitrary shell commands
- Test edge cases and error conditions
Security updates will be:
- Released as soon as possible
- Clearly marked in release notes
- Accompanied by detailed advisory information
- Communicated through GitHub Security Advisories
For security-related questions that don't involve vulnerabilities, please:
- Open a GitHub Discussion
- Tag your question with "security"
- We'll respond publicly when appropriate