Library comparison
capacitor-health vs @capgo/capacitor-health
Registry data read 2026-10-03
Both are Capacitor plugins that cover Apple HealthKit and Health Connect behind one TypeScript API, and both declare iOS and Android native code. The visible differences are the licence (MIT for capacitor-health, MPL-2.0 for @capgo/capacitor-health, per npm), who publishes it (mley/capacitor-health versus Capgo, whose README also advertises Capgo's app-update and plugin-building services), and the limits each README documents, set out below — including Health Connect history, which only one of them requests.
Side by side
Every cell is read from the registries and the repositories by a script. There is no winner row.
| Fact | capacitor-health | @capgo/capacitor-health |
|---|---|---|
| Registry | npm: capacitor-health | npm: @capgo/capacitor-health |
| Latest version | 8.4.0 | 8.11.4 |
| Latest published | 2026-09-23 (10 days before our 2026-10-03 read) | 2026-09-22 (11 days before our 2026-10-03 read) |
| First published | 2024-10-02 | 2025-09-24 |
| Versions published | 23 | 99 |
| Licence | MIT (package.json license) | MPL-2.0 (package.json license) |
| Platforms | ios, android (package.json "capacitor" keys: ios, android) | ios, android (package.json "capacitor" keys: ios, android) |
| Requires | @capacitor/core >=8.0.0 (package.json peerDependencies) | @capacitor/core >=8.0.0 (package.json peerDependencies) |
| Deprecated | no deprecation in the registry | no deprecation in the registry |
| Status classifier | — | — |
| Last commit, default branch | 2026-09-23 | 2026-09-22 |
| GitHub stars / archived | 20 stars · not archived (read 2026-10-03) | 31 stars · not archived (read 2026-10-03) |
What each README says
capacitor-health
How to choose: our reading
Judgement, labelled as such, drawn only from the facts above.
- Your organisation keeps a licence allow-list: compare the licence row first. Different licences carry different obligations, and that decision belongs to whoever owns your licence policy, not to a feature table.
- You chart hourly data on Android: capacitor-health's README documents day-only buckets there, so plan to bucket raw records yourself; @capgo/capacitor-health's README lists the types it cannot aggregate at all.
- You need Health Connect history beyond the default window: @capgo/capacitor-health documents a requestHistoryAccess option for it, and capacitor-health's README says its queries do not request that permission.
- Check that the plugin's peer dependency matches your Capacitor major before either one.
Questions
- Are capacitor-health and @capgo/capacitor-health the same plugin?
- No. They are separate packages from separate repositories, mley/capacitor-health and Cap-go/capacitor-health, with different licences in their npm metadata and different documented APIs. capacitor-health's README credits cordova-plugin-health for some of its ideas; @capgo/capacitor-health's README does not describe a shared origin.
- Which Capacitor health plugin can read more than 30 days of Health Connect data?
- @capgo/capacitor-health, through a requestHistoryAccess option that also requests READ_HEALTH_DATA_HISTORY, which the app must declare in its manifest. capacitor-health's README says the opposite of itself: its queries do not request READ_HEALTH_DATA_HISTORY, so Health Connect only returns data from 30 days before the permission was first granted.