rozmova-analytics@1.1.65
A collection of JavaScript functions for Rozmova analytics
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected network and browser-storage behavior is consistent with the analytics API, with no concrete credential theft, install abuse, or malicious execution identified. The consent defect merits application-level correction but does not establish malware intent.
Decision evidence
public snapshot- package.json has build and maintenance scripts, with no automatic install lifecycle hooks or runtime self-dependency.
- Analytics initialization is caller-invoked in both runtime entrypoints.
- First-party event requests use fixed Rozmova or Clearly production and staging hosts.
- Profile identification receives user data supplied by the caller.
- The dynamically loaded Customer.io script implements the package's analytics integration.
- The cookie-consent rejection callback grants Google tracking consent, a privacy implementation defect.
- Initialization enables third-party analytics, and callers can override Mixpanel configuration.
Source & flagged code
6 flaggedpackage.json has build and maintenance scripts, with no automatic install lifecycle hooks or runtime self-dependency.
package.jsonView on unpkg · L46Analytics initialization is caller-invoked in both runtime entrypoints.
dist/index.cjsView on unpkg · L690Findings
Affected versions and remediation
This report applies to rozmova-analytics@1.1.65.
See all versions of rozmova-analytics for other recorded verdicts.
- Review the evidence and your use of rozmova-analytics@1.1.65 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.