We release security updates for the latest stable version only. Please ensure you're running the most recent version before reporting issues.
| Version | Supported |
|---|---|
| 1.6.x | ✅ |
| < 1.6 | ❌ |
We take security seriously. If you discover a security vulnerability, please report it responsibly.
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, use GitHub's private security advisory feature:
- Go to the Security tab
- Click "Report a vulnerability"
- Provide detailed information about the vulnerability
To help us assess and address the issue quickly, please include:
- Type of vulnerability (e.g., credential exposure, code injection, privilege escalation)
- Step-by-step reproduction instructions
- Affected versions (if known)
- Potential impact assessment
- Proof of concept code (if applicable)
- Suggested fix (if you have one)
- Acknowledgment: Within 24-48 hours
- Initial assessment: Within 1 week
- Resolution timeline: Depends on severity and complexity
We'll keep you informed throughout the process and credit you in the security advisory and release notes (unless you prefer to remain anonymous).
- Session keys are stored locally in
~/.claude-session-key - File permissions are automatically set to
0600(owner read/write only) - Keys are never transmitted except to
claude.aivia HTTPS - No cloud sync or external storage
- The app is currently unsigned (no Apple Developer certificate)
- macOS Gatekeeper will block the app on first launch
- Users must manually approve via System Settings → Privacy & Security
- This is expected behavior for community open-source apps
- All communication uses HTTPS only
- API requests are sent exclusively to
claude.aiendpoints - No telemetry, analytics, or third-party tracking
- Session authentication via secure cookies only
- Claude Code integration scripts are installed to
~/.claude/ - Script permissions are set to
755(read/execute for all, write for owner) - Scripts only read the existing session key file
- No arbitrary code execution from external sources
- App Sandbox is disabled to allow file system access
- Required for reading
~/.claude-session-keyand writing~/.claude/scripts - Necessary trade-off for the app's core functionality
- Never share your session key publicly
- Treat it like a password
- Rotate it if you suspect compromise (extract a fresh key from claude.ai)
- Check file permissions:
ls -la ~/.claude-session-keyshould show-rw-------
- Download only from official sources:
- Build from source if you prefer:
git clone+ Xcode build
- Security patches are released for the latest version only
- Enable notifications for new releases on GitHub
- Review the CHANGELOG.md for security-related updates
We recognize and appreciate security researchers who help keep our community safe. Contributors who responsibly disclose vulnerabilities will be:
- Credited in the security advisory (with permission)
- Acknowledged in release notes
- Listed as security contributors in the project
Thank you for helping keep Claude Usage Tracker secure!
For non-security related issues, please use GitHub Issues.
For general questions, see our Contributing Guide.