@hmscore/react-native-hms-analytics@6.12.0-302
React Native HMS Analytics Kit
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found a conventional React Native analytics wrapper with no lifecycle hooks or malicious execution primitives. The flagged example is a demo that calls the same analytics API exposed by the package.
Decision evidence
public snapshot- The manifest declares a React Native library entry and contains no lifecycle-script field.
- The flagged demo initializes HMS Analytics only when its Android component mounts.
- The JavaScript API delegates calls to the React Native native module.
- The Android provider is not exported and initializes the declared HiAnalytics SDK.
- No install-time code, shell execution, dynamic evaluation, credential harvesting, or package-owned network client was found.
- Analytics and identifier APIs are exposed as explicit app-facing SDK calls; no unrelated file or project mutation was found.
Source & flagged code
8 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-analytics@6.12.0-302.
See all versions of @hmscore/react-native-hms-analytics for other recorded verdicts.
- Review the evidence and your use of @hmscore/react-native-hms-analytics@6.12.0-302 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.