We provide security updates for the following versions:

We take security vulnerabilities seriously. If you discover a security vulnerability, please follow these steps:

Do not open a public GitHub issue for security vulnerabilities. This could put users at risk.

Please report security vulnerabilities by emailing the maintainers directly or through a private security channel.

Include the following information:

• Description of the vulnerability
• Steps to reproduce
• Potential impact
• Suggested fix (if any)

• Initial Response: Within 48 hours
• Status Update: Within 7 days
• Fix Timeline: Depends on severity and complexity

We will coordinate disclosure with you after the vulnerability is fixed. We appreciate responsible disclosure.

1. Keep Dependencies Updated: Regularly update dependencies
2. Use Virtual Environments: Isolate Python dependencies
3. Review Code: Review code before running benchmarks
4. Limit Network Access: Benchmarks run locally by default
5. Monitor Resources: Monitor resource usage during benchmarks

1. Input Validation: Validate all inputs
2. Resource Limits: Implement resource limits
3. Error Handling: Handle errors gracefully
4. No Secrets: Never commit secrets or credentials
5. Dependency Review: Review dependencies for vulnerabilities

• Benchmarks execute locally on your machine
• No external network access required (except Ollama)
• All data stays local

• Benchmarks connect to local Ollama instances
• No authentication required (local only)
• Ensure Ollama is not exposed to network

• Benchmarks may use significant CPU/GPU resources
• Monitor system resources during execution
• Implement resource limits if needed

• All benchmark data stored locally
• No data transmitted externally
• Review data before sharing

Security updates will be:

• Released as patch versions (e.g., 1.0.1)
• Documented in CHANGELOG.md
• Tagged with security label
• Communicated to users

For security concerns, contact:

• GitHub: Open a private security advisory

Last Updated: January 2025