| Version | Supported |
|---|---|
| 0.1.x | ✅ |
We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report through GitHub's private vulnerability reporting feature.
When reporting, please include:
- A description of the vulnerability
- Steps to reproduce the issue
- Potential impact of the vulnerability
- Any suggested fixes (if available)
- Acknowledgment: We will acknowledge receipt of your report within 48 hours.
- Assessment: We will assess the vulnerability and determine its severity.
- Updates: We will keep you informed of our progress.
- Resolution: Once fixed, we will notify you and credit you (unless you prefer anonymity).
- We follow coordinated disclosure practices
- We aim to release patches within 90 days of confirmed vulnerabilities
- We will publicly disclose vulnerabilities after a fix is available
When using mcpbr:
- API Keys: Never commit API keys to version control. Use environment variables.
- Docker: Ensure Docker is properly secured on your system.
- MCP Servers: Only use trusted MCP servers from verified sources.
- Network: Be aware that MCP servers may have network access within their containers.
We regularly update dependencies to address known vulnerabilities. You can check for outdated packages with:
pip list --outdatedThank you for helping keep mcpbr secure!