cordova-plugin-health
JavaScript · npm: cordova-plugin-health · latest 3.3.0 (2026-09-26) · registry read 2026-10-03
What it wraps
Apple HealthKit on iOS and Google Health Connect on Android. The README says version 3 is a complete rewrite of the Android side for the Health Connect API.
“A plugin that abstracts fitness and health repositories like Apple HealthKit or Google Health Connect.”
Source: README
Named in the registry description: Apple HealthKit, Health Connect.
Install
Cordova
cordova plugin add cordova-plugin-health --variable HEALTH_READ_PERMISSION='App needs read access' --variable HEALTH_WRITE_PERMISSION='App needs write access' --variable HEALTH_CONNECT_CLIENT_VERSION='1.2.0-alpha06'From the README
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: cordova-plugin-health
- Latest version
- 3.3.0, published 2026-09-267 days before our 2026-10-03 read
- First published
- 2016-01-12 · 50 versions published
- Licence
- MITpackage.json license
- Platforms
- Android, iOSpackage.json engines.cordovaDependencies names cordova-android, cordova-ios
- Requires
- cordova >12.0.0 · cordova-ios >7.0.0 · cordova-android >12.0.0package.json engines.cordovaDependencies["3.0.0"]
- Repository
- dariosalvi78/cordova-plugin-health
- Last commit, default branch
- 2026-10-03on the day of our read · read by git on 2026-10-03
- GitHub signals
- 192 stars · 28 open issues and PRs · not archived · last push to any branch 2026-10-03GitHub API, read 2026-10-03
Registry description: “A plugin that abstracts fitness and health repositories like Apple HealthKit or Google 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.
Permissions are yours to declare. The README says the list is too long to add them all, and that listing every permission may be problematic when submitting to the Play Store.
“This plugin will NOT ADD PERMISSIONS for the data types that you need”
Source: README
Google Fit is gone from v3. The README says Fit is no longer supported and that anyone who still wants it must use version 2.1.1.
Source: README
A privacy policy page is mandatory on Android. The README says the plugin shows
privacypolicy.htmlfrom the project'swwwfolder in a webview with JavaScript disabled when Health Connect asks for it.Source: README
Screen lock. The README notes that Health Connect requires the user to have a screen lock set with a PIN, pattern or password.
Source: README
Capacitor needs manual edits. The README's Capacitor section, written against plugin v3.1.0 and @capacitor/android 5.5.1, says Capacitor does not apply this plugin's manifest and Gradle changes automatically and lists them step by step.
Source: README
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.
- Migrate from Google Fit to Health Connect →What changed for apps that used this plugin's Fit-era version 2.
Other Capacitor and Cordova packages on this list
Capacitor and Cordova health plugins: every package side by side, and how to choose →
- capacitor-health8.4.0 · 2026-09-23Apple HealthKit on iOS and Health Connect on Android.
- @capgo/capacitor-health8.11.4 · 2026-09-22Apple 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.
Questions
- Does cordova-plugin-health still support Google Fit?
- No. The README says version 3 rewrote the Android side for Health Connect and that Google Fit is no longer supported; it points anyone who still needs Fit to version 2.1.1. Google's Fit migration guide says the Fit API will only be supported until the end of 2026.
- Can I use cordova-plugin-health in a Capacitor app?
- Yes, with manual steps. The README has a Capacitor section, based on plugin v3.1.0 and @capacitor/android 5.5.1, explaining that Capacitor does not apply the plugin's AndroidManifest.xml and Gradle changes automatically, and listing the privacy-policy activity, the Health Connect package query and the permissions to add by hand.
- Why does cordova-plugin-health not ask for any Health Connect permissions?
- Because it declares none for you. The README says the plugin will not add permissions for the data types you need, and that you must add each one to AndroidManifest.xml yourself, preferably through config.xml so that the permissions survive removing and re-adding the Android platform.
Registry facts read by scripts/fetch-libraries.mjs on 2026-10-03 and refreshed weekly; the latest release was published 7 days before our 2026-10-03 read. README quotes identify the project’s own statements; the selection, grouping and comparisons are AIFitnessAPI’s. For tagged releases of the main bridges, see the SDK release tracker.