@hmscore/react-native-hms-awareness@3.8.0-303
React Native HMS Awareness Kit
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source enables Huawei analytics by default and sends runtime app and device metadata during Awareness API use. The package does not document this telemetry, so this is suspicious rather than a confirmed malicious data theft; no analytics host is hard-coded in the reviewed source.
Decision evidence
public snapshot- The logger initializes Huawei analytics and enables logging by default when first created.
- Calling an Awareness capture method starts logging and sends an event after the API succeeds.
- The event maps include app ID, app package and version, API name, result, call time, device model and network type.
- The package exposes a method to disable logging, but the README does not document the telemetry.
- The package has no lifecycle scripts, and its JavaScript entry point only exports native modules.
- Telemetry is tied to calls to Awareness APIs; the logger code does not include location or other capture results in its event maps.
- The package provides an explicit disableLogger method.
Source & flagged code
7 flaggedPackage ships non-JavaScript build or shell helper files.
example/android/gradlew.batView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
example/App.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hmscore/react-native-hms-awareness@3.8.0-303.
See all versions of @hmscore/react-native-hms-awareness for other recorded verdicts.
- Review the evidence and your use of @hmscore/react-native-hms-awareness@3.8.0-303 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.