@meetelise/chat@1.56.0
### Installation
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s chat analytics automatically sends visitor browsing context and identifiers to the publisher’s endpoint, with no visible consent or opt-out in the inspected code. This is a runtime telemetry concern, not evidence of credential theft or unrelated collection.
Decision evidence
public snapshot- The analytics module posts to app.meetelise.com with the current page URL, referrer, organization, building, and chat ID.
- Chat initialization sends a heartbeat automatically on 5% of initializations.
- The package is a MeetElise chat widget, and the analytics endpoint belongs to its publisher’s service.
- The postinstall script only runs sort-package-json; prepare installs Husky.
- The documented runtime entry is MEChat.start(), which callers invoke to add the chat widget.
Source & flagged code
4 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references a known benign dynamic code generation pattern.
public/dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @meetelise/chat@1.56.0.
See all versions of @meetelise/chat for other recorded verdicts.
- Review the evidence and your use of @meetelise/chat@1.56.0 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.