Caveat verdict

garmin-connect-health

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Fetches Garmin Connect health metrics locally using garminconnect library and stores them in local JSON/SQLite; credentials are kept local via environment variables, keychain, or credential file — no external exfiltration.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

23
security
90
transparency
90
maintenance

Permission integrity

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (5)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · PASSWORD="yourpassword

Pattern match high

Accesses shell history/config

README.md · code · ~/.zshrc

Pattern match medium

Accesses system credential store

SKILL.md · prose · downgraded · Keychain

Pattern match medium

subprocess execution — runs system commands from Python

garmin_health.py · prose · downgraded · subprocess.run(

Pattern match low

Python os.environ.get — reads environment variable

garmin_health.py · prose · downgraded · os.environ.get(

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

package_install

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API