We release patches for security vulnerabilities in the following versions:
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
If you discover a security vulnerability, please follow these steps:
- Do not open a public issue
- Email the security team at: security@example.com
- 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
- Resolution: Within 30 days (depending on complexity)
When using this MCP server:
- Never commit API tokens or credentials to version control
- Use environment variables for sensitive configuration
- Regularly rotate your Jira API tokens
- Limit permissions of your API tokens to minimum required
- Monitor usage of your API tokens
- Keep dependencies up to date
# ✅ Good - Use environment variables
export JIRA_API_TOKEN="your-token-here"
# ❌ Bad - Never hardcode in source code
const token = "your-token-here";We take security seriously. If you find a security vulnerability, please report it responsibly:
- Email: security@example.com
- Subject: [SECURITY] Brief description
- Include: Detailed steps to reproduce
- Do not: Disclose publicly until we've had a chance to fix it
We appreciate the security research community and responsible disclosure. Contributors who report valid security vulnerabilities will be acknowledged in our security advisories (with their permission).
Security updates will be released as patch versions (e.g., 1.0.1, 1.0.2) and will be clearly marked in the changelog.
For security-related questions or concerns, please contact:
- Email: security@example.com
- GitHub: Create a private security advisory