| Version | Supported |
|---|---|
| 1.x | Yes |
If you discover a security vulnerability in this project, please report it responsibly:
- Do not open a public issue.
- Email us at security@hol.org with details.
- Include steps to reproduce, expected vs actual behavior, and potential impact.
- We will acknowledge within 48 hours and aim to resolve within 7 days.
This tool helps you follow security best practices for Codex plugins. For the latest guidance, see the Codex Security documentation.
- Never commit API keys, tokens, or secrets to your repository.
- Use environment variables for sensitive configuration.
- Avoid dangerous shell commands in
.mcp.jsonconfigurations. - Include a
SECURITY.mdin your plugin repository. - Use permissive licenses (Apache-2.0 or MIT) for clarity.
- This scanner checks for common patterns but does not guarantee security.
- Always review plugin code manually before installation.
- Keep this tool updated for the latest check definitions.