@capgo/capacitor-health

Install

npm install @capgo/capacitor-health

npx cap sync

Registry and repository facts

Read from npm and the repository by a script, not typed by hand. Where the metadata does not state something, the row says so. Dates are shown as dates, with the gap to our read, rather than as a verdict on whether the project is alive.

Registry

npm: @capgo/capacitor-health

Latest version

8.11.4, published 2026-09-2211 days before our 2026-10-03 read

First published

2025-09-24 · 99 versions published

Licence

MPL-2.0package.json license

Platforms

iOS, Androidpackage.json "capacitor" keys: ios, android

Requires

@capacitor/core >=8.0.0package.json peerDependencies

Repository

Cap-go/capacitor-health

Last commit, default branch

2026-09-2211 days before our 2026-10-03 read · read by git on 2026-10-03

GitHub signals

31 stars · 2 open issues and PRs · not archived · last push to any branch 2026-09-25GitHub API, read 2026-10-03

Registry description: “Capacitor plugin to interact with data from Apple HealthKit and Health Connect”

What the README warns about

Each item is the project’s own statement, checked on 2026-10-03, quoted where the wording matters.

• Match the plugin major to Capacitor. The README's compatibility table marks v8 maintained, v7 maintained on demand, and v6 and v5 unmaintained.

  “Only the latest major version is actively maintained.”

  Source: README

• The 30-day window. The README documents a requestHistoryAccess option that also requests READ_HEALTH_DATA_HISTORY, which the app must declare in its manifest, and says the permission only exists on sufficiently new Health Connect providers.

  “Without it, Health Connect caps reads to roughly the last 30 days; granting it lets you read older data.”

  Source: README

• No aggregation for some types. The README says aggregated queries are not supported for sleep, respiratory rate, oxygen saturation, heart rate variability and VO2 max, which should use readSamples() instead.

  Source: README

• A claim to read with the list beside it. The README calls this "the only free, unified health data plugin for Capacitor". capacitor-health (MIT) and cordova-plugin-health (MIT), both listed here, also cover both stores according to their READMEs and npm metadata.

  Source: README and npm metadata

The API underneath

A wrapper inherits every rule of the API it calls. These pages cover that layer directly.

• Health Connect integration guide →The Android API these packages wrap: permissions, records, the 30-day window.
• Health Connect record reference →Every record class with Google's fields, permission strings and aggregate metrics — check the type you need exists before blaming the wrapper.
• HealthKit integration guide →The native API every iOS package here calls into: authorization, queries, background delivery.
• HealthKit ↔ Health Connect type matrix →The cross-platform pairs a unified plugin has to reconcile.

Other Capacitor and Cordova packages on this list

Capacitor and Cordova health plugins: every package side by side, and how to choose →

• capacitor-health vs @capgo/capacitor-health: side by side →

• capacitor-health8.4.0 · 2026-09-23Apple HealthKit on iOS and Health Connect on Android.
• @perfood/capacitor-healthkit1.3.2 · 2025-02-13Apple HealthKit only: its package metadata declares iOS native code and nothing for Android.
• cordova-plugin-health3.3.0 · 2026-09-26Apple HealthKit on iOS and Google Health Connect on Android.

Questions

Which @capgo/capacitor-health version matches my Capacitor version?

The one with the same major version. The README says the plugin's major version follows Capacitor's, so plugin v8 is for Capacitor 8, and that only the latest major is actively maintained: v7 is maintained on demand and v6 and v5 are not maintained.

Why does @capgo/capacitor-health only return 30 days of Android data?

The README says Health Connect caps reads to roughly the last 30 days unless the READ_HEALTH_DATA_HISTORY permission is granted. Set requestHistoryAccess on the authorization request and declare the permission in AndroidManifest.xml; on providers too old to support it, the README says the returned status reports historyAccessAvailable as false.