Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI agent developers, personal AI tool builders, fitness / health data analysts, and power users who need a CLI-friendly interface to their own Google Health data (steps, heart rate, sleep, SpO2, HRV, ECG, blood glucose, nutrition) that an AI agent can drive deterministically. The durable differentiator is the 40 verified data types + agent-friendly JSON output + deterministic exit codes
Who should use it
Who should skip it
Consider Google-Health-API/google-health-cli lower priority if you already have a working solution in this category.
About this signal
Google-Health-API/google-health-cli is tracked by RepoRadar as a go cli for google health api v4 in the Developer Tools section. It was first seen on 2026-07-04 and last updated on 2026-07-04. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for Google-Health-API/google-health-cli are workflow potential (9.4) and open-source/build quality (8.4), while maturity (5.8) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Google-Health-API/google-health-cli a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Setup requires a GCP project + Health API enabled + OAuth Desktop client credentials — a non-trivial one-time cost that takes 10-15 minutes for users unfamiliar with Google Cloud Console; budget the setup time and follow the README's step-by-step; OAuth tokens are stored at `~/.config/ghealth/credentials.json` with mode 0600 — keep this file's permissions intact and don't commit it; the auto-refresh handles expiration but a manual `ghealth auth login` may be needed if the refresh token is revoked.