Skip to content

Security: drosam/gitpulse

SECURITY.md

Security policy

Reporting a vulnerability

Please report vulnerabilities privately through GitHub private vulnerability reporting. Do not open a public issue.

Include the GitPulse version (shown in the menu bar menu), your macOS version, steps to reproduce, and the impact you expect. You should get a reply within a week.

Supported versions

Only the latest release receives fixes.

How GitPulse handles your token

  • The token comes from GITHUB_TOKEN, the macOS Keychain, gh auth token, or GitHub's OAuth device flow.
  • Device-flow tokens are stored only in your login Keychain (service dev.davidrosa.gitpulse.github-token).
  • The token is sent only to api.github.com. The device flow talks only to github.com.
  • Requests use no disk cache or cookie store. v0.1.0 cached requests, including the token, in ~/Library/Caches/dev.davidrosa.gitpulse; later versions delete that folder and ~/Library/HTTPStorages/dev.davidrosa.gitpulse at launch.
  • GitPulse has no servers, analytics, or telemetry.
  • Remove the Keychain item with security delete-generic-password -s dev.davidrosa.gitpulse.github-token.

There aren't any published security advisories