stream-chat@9.54.3
JS SDK for the Stream Chat API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe connection diagnostics are opt-in, but their payload includes the user token and other identifying details and the option declaration does not disclose those fields. This is a real sensitive-data risk, though the code gates transmission on enableInsights rather than sending it by default.
Decision evidence
public snapshot- When enableInsights is enabled, a failed WebSocket connection triggers an insights submission.
- The insights payload includes the API key and user token, along with user and connection details.
- The insights are posted to https://chat-insights.getstream.io/insights/<type>.
- The insight option is opt-in, but its type declaration does not describe the sensitive fields sent.
- The manifest’s postinstall only conditionally imports scripts/install-husky.mjs; that file is absent from the package snapshot, which lists only dist and src.
- The connection failure path gates insight submission on enableInsights.
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.3.
See all versions of stream-chat for other recorded verdicts.
- Review the evidence and your use of stream-chat@9.54.3 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.