stream-chat@9.54.4
JS SDK for the Stream Chat API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s install scripts do not show an attack, and insight reporting is disabled by default. When explicitly enabled, though, the telemetry sends the chat token and user details to an analytics endpoint without source evidence describing that collection, warranting a warning.
Decision evidence
public snapshot- When enabled, websocket failure and recovery paths submit insight reports.
- The report includes the chat token, user details, device data and websocket details.
- Reports are sent to chat-insights.getstream.io.
- Insight reporting is gated by the opt-in enableInsights option, which is not enabled in the constructor defaults.
- The reporting endpoint is a GetStream-owned host, and the package postinstall only imports its Husky setup script if that file exists.
Source & flagged code
5 flaggedInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to stream-chat@9.54.4.
See all versions of stream-chat for other recorded verdicts.
- Review the evidence and your use of stream-chat@9.54.4 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.