Skip to content

Security: danielalanbates/Claude-Usage-Tracker

Security

SECURITY.md

Security Policy

Supported Versions

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

Download the latest version

Reporting a Vulnerability

We take security seriously. If you discover a security vulnerability, please report it responsibly.

How to Report

Please do NOT report security vulnerabilities through public GitHub issues.

Instead, use GitHub's private security advisory feature:

  1. Go to the Security tab
  2. Click "Report a vulnerability"
  3. Provide detailed information about the vulnerability

What to Include

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)

Response Timeline

  • 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).

Security Considerations

Session Key Storage

  • 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.ai via HTTPS
  • No cloud sync or external storage

Application Signing

  • 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

Network Security

  • All communication uses HTTPS only
  • API requests are sent exclusively to claude.ai endpoints
  • No telemetry, analytics, or third-party tracking
  • Session authentication via secure cookies only

Code Execution

  • 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

Sandboxing

  • App Sandbox is disabled to allow file system access
  • Required for reading ~/.claude-session-key and writing ~/.claude/ scripts
  • Necessary trade-off for the app's core functionality

Best Practices for Users

Protect Your Session Key

  • 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-key should show -rw-------

Verify Downloads

Keep Updated

  • Security patches are released for the latest version only
  • Enable notifications for new releases on GitHub
  • Review the CHANGELOG.md for security-related updates

Security Acknowledgments

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!

Questions?

For non-security related issues, please use GitHub Issues.

For general questions, see our Contributing Guide.

There aren’t any published security advisories