Skip to content

Security: 0xBreadguy/garmin-data-workbench

SECURITY.md

Security and privacy

Keep keys, tokens, health records, original activity files and GPS routes out of Git, public reports and logs. Use synthetic reproductions.

Report a vulnerability

Use GitHub private vulnerability reporting. If that route is unavailable, open an issue requesting a private channel, without exploit details or sensitive data.

Privately provide the source revision, affected component, impact and a synthetic reproduction. Don't attach an archive or credentials. Fixes target current code unless a maintainer says otherwise; no response time or older-release support is promised.

Revoke or replace exposed credentials through Garmin. Removing a file or message doesn't revoke a key.

Choose the host

Processes sharing your OS user can read owner-only files. Accept that access model before remote authentication or sync. Query results may reach the selected AI provider. The stdio server provides no authenticated remote connector. See setup.

There aren't any published security advisories