Case file No.373 · pypi · stdio

Garmin Connect

io.github.happyc0der/garmin-connect-api · v0.3.1

Read and write Garmin Connect: activities, strength sets, health data, workouts and weigh-ins.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 0 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

314 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v0.3.1)Oct 20, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Garmin Connect safe?

MCPWatch gives Garmin Connect a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Garmin Connect have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package garmin-connect-api. That is not proof of safety.

When was Garmin Connect last updated?

The latest registry version is 0.3.1, published Oct 20, 2026. The last push to happyc0der/garmin-connect-api was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Garmin Connect use?

GitHub reports the license of happyc0der/garmin-connect-api as MIT.

Related servers

same publisher / similar score