claudex/SECURITY.md
Nenad Ilic 57dac558f4 Prepare project for GitHub publishing
- Update README with detailed usage instructions
- Add GitHub community files (CONTRIBUTING, CODE_OF_CONDUCT, etc.)
- Set up CI workflows for automated testing
- Create CHANGELOG for version tracking
- Add SECURITY guidelines
- Update licensing and author information
2025-04-26 14:42:48 +02:00

930 B

Security Policy

Reporting a Vulnerability

If you discover a security vulnerability in claudex, please report it by creating a new issue with the label "security".

Please include the following information in your report:

  • A description of the vulnerability
  • Steps to reproduce the issue
  • Potential impact of the vulnerability
  • Any suggestions for remediation if applicable

We take security issues seriously and will respond as quickly as possible to address any concerns.

Supported Versions

Only the latest version of claudex is currently supported with security updates.

Security Best Practices

When using claudex:

  1. Never commit API keys or sensitive information to your repository
  2. Always use environment variables for configuration as shown in the documentation
  3. Keep dependencies updated to the latest secure versions
  4. Properly secure your API endpoints when deploying to production environments