| Version | Supported |
|---|---|
| 1.x | Yes |
| < 1.0 | No |
Please do not report security vulnerabilities through public GitHub issues.
-
GitHub Security Advisories (recommended): Use the Security Advisories feature to report vulnerabilities privately.
-
Contact Form: Send details to https://effortlesssteven.com/about/
- Description of the vulnerability
- Steps to reproduce or proof-of-concept
- Potential impact assessment
- Any suggested fixes (optional)
- Acknowledgment: Within 48 hours
- Initial Assessment: Within 7 days
- Resolution: Within 30 days for critical issues, 90 days for lower severity
The following are considered security vulnerabilities for tokmd:
- Path traversal: Operations that access files outside intended directories
- Arbitrary code execution: Malicious input causing unintended code execution
- Denial of service: Input causing crashes, infinite loops, or excessive resource consumption
- Information disclosure: Unintended exposure of sensitive file contents or system information
- Command injection: Unsanitized input passed to shell commands or external processes
- Issues in unsupported versions
- Theoretical attacks without a realistic exploitation scenario
- Performance issues that do not constitute denial of service
- Bugs in third-party dependencies (report these upstream, but feel free to notify us)
- We will acknowledge receipt of your report promptly.
- We will investigate and determine the severity and scope.
- We will develop and test a fix.
- We will coordinate disclosure timing with you.
- We will credit you in the release notes (unless you prefer anonymity).
Thank you for helping keep tokmd secure.