| Version | Supported |
|---|---|
| 1.x.x | ✅ |
If you discover a security vulnerability in this project, please report it responsibly:
- Do not open a public GitHub issue for security vulnerabilities
- Email the maintainers directly or use GitHub's private vulnerability reporting
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
We will acknowledge receipt within 48 hours and aim to provide a fix within 7 days for critical issues.
- Never commit
.envfiles containing real API keys - Use
config.example.envas a template with placeholder values - Rotate API keys immediately if accidentally exposed
- This application monitors keystrokes system-wide for its core functionality
- Privacy filters exclude sensitive windows (banks, password managers)
keylog.jsonstores typed text locally only - no data is sent externally except to AI APIs- Users should be aware of the keylogging functionality
- All data is stored locally on the user's machine
- No telemetry or analytics are collected
- AI requests are sent only to the configured API provider (Mistral by default)
- Current implementation uses
nodeIntegration: truefor simplicity - For hardened deployments, consider enabling
contextIsolationand using preload scripts
- Keep API keys in
.envfile only (never share or commit) - Review the privacy filters in
keystroke_monitor/config.py - Clear
keylog.jsonperiodically if desired - Use on trusted machines only (keystroke monitoring is powerful)
- Keep dependencies updated (
npm update,pip install -U -r requirements.txt)