@perfood/capacitor-healthkit
JavaScript · npm: @perfood/capacitor-healthkit · latest 1.3.2 (2025-02-13) · registry read 2026-10-03
What it wraps
Apple HealthKit only: its package metadata declares iOS native code and nothing for Android. The README adds that it covers only part of HealthKit for now.
“Disclaimer : for now only some of the HK data base, in the future the retrieve base will be bigger !”
Source: README
Named in the registry description: Apple HealthKit.
Install
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.
- Latest version
- 1.3.2, published 2025-02-13597 days before our 2026-10-03 read
- First published
- 2022-05-02 · 14 versions published
- Licence
- MITpackage.json license
- Platforms
- iOSpackage.json "capacitor" keys: ios
- Requires
- @capacitor/core ^4.0.0package.json peerDependencies
- Repository
- perfood/capacitor-healthkit
- Last commit, default branch
- 2025-02-13597 days before our 2026-10-03 read · read by git on 2026-10-03
- GitHub signals
- 89 stars · 13 open issues and PRs · not archived · last push to any branch 2025-02-13GitHub API, read 2026-10-03
Registry description: “Capacitor plugin to read data from and write data to Apple Health”
What the README warns about
Each item is the project’s own statement, checked on 2026-10-03, quoted where the wording matters.
Main is frozen; v2 is in alpha.
“We are slowly working on the next version of this plugin. PRs to the main branch are no longer being accepted, please work with the v2 branch from now on. v2 is already being published as alpha on npm.”
Source: README
The registry's dist-tags at our last read:
beta→ 1.1.0-2,next→ 2.0.0-alpha.2,latest→ 1.3.2.Source: npm registry
The API underneath
A wrapper inherits every rule of the API it calls. These pages cover that layer directly.
- HealthKit integration guide →The native API every iOS package here calls into: authorization, queries, background delivery.
- HealthKit data types by group →Apple's identifiers grouped the way Apple groups them — check the type you need exists before blaming the bridge.
- Every HealthKit error code →What the HKError a bridge passes through actually means.
- HealthKit permission builder →The Info.plist keys and read/share sets any HealthKit plugin needs.
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.
- cordova-plugin-health3.3.0 · 2026-09-26Apple HealthKit on iOS and Google Health Connect on Android.
Questions
- Does @perfood/capacitor-healthkit support Android?
- No. Its package metadata declares iOS native code only, and the README covers Apple Health setup alone. For Health Connect on Android in a Capacitor app, the cross-platform options listed here are capacitor-health, @capgo/capacitor-health and cordova-plugin-health.
- Is there a newer version of @perfood/capacitor-healthkit?
- The README says v2 is being published as an alpha on npm and asks contributors to work on the v2 branch. At our last read of the registry the next tag pointed to 2.0.0-alpha.2 while latest pointed to 1.3.2.
Registry facts read by scripts/fetch-libraries.mjs on 2026-10-03 and refreshed weekly; the latest release was published 597 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.