@meetelise/chat@1.58.0
### Installation
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package performs sampled runtime analytics to its own service, but sends page and attribution context and exposes no evident way to disable it. This is a warning-level telemetry concern; the inspected install hooks are development tooling and showed no install-time data transfer.
Decision evidence
public snapshot- Chat initialization sends a heartbeat to MeetElise’s analytics endpoint.
- The heartbeat runs automatically on chat initialization for a 5% sample.
- The analytics payload includes the page URL, referrer, organization, building, chat ID and campaign sources.
- The package’s install scripts run package sorting and Husky setup; no install-time data transfer was identified.
- The analytics request goes to the package’s own MeetElise service and is tied to webchat functionality.
- The webchat is initialized through the exported start method.
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.58.0.
See all versions of @meetelise/chat for other recorded verdicts.
- Review the evidence and your use of @meetelise/chat@1.58.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.