stream-chat@9.54.1
JS SDK for the Stream Chat API
AI Security Review
scanned 6d ago · by lpm-firewall-aiInsight reporting is opt-in, but its payload includes an authentication token and user details sent to the vendor's insights endpoint without source-level disclosure of those fields. The lifecycle alert is not evidence of an install-time attack: postinstall conditionally imports a Husky script, while the package file list omits `scripts`.
Decision evidence
public snapshot- With `enableInsights` enabled, connection failures and recovery events trigger insight reports.
- The insight payload includes the Stream token, user details, API key, device data and connection details.
- Reports are sent to `chat-insights.getstream.io`; the package source does not document the sensitive fields included.
- The package is a JavaScript SDK for the Stream Chat API, and its normal networking supports that purpose.
- The postinstall script only imports a Husky setup file if it exists; the package file list includes `dist` and `src`, not `scripts`.
- Insight reporting is gated by the explicit `enableInsights` option and relevant connection events; it is not enabled by the shown defaults.
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.1.
See all versions of stream-chat for other recorded verdicts.
- Review the evidence and your use of stream-chat@9.54.1 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.