registry / stream-chat / 9.50.2
stream-chat@9.50.2
JS SDK for the Stream Chat API
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe scanner's lifecycle finding is a false positive for this published artifact: its guarded Husky helper is absent, so postinstall performs no mutation. Source inspection shows normal, explicitly invoked chat SDK networking and no concrete malicious chain.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Client construction followed by explicit Stream Chat API or WebSocket use; package installation only evaluates the inert postinstall guard.
Impact
No confirmed unconsented execution, persistence, file mutation, credential exfiltration, or remote payload loading.
Mechanism
explicit SDK HTTP/WebSocket requests to the configured Stream Chat endpoint
AI rationale
The scanner's lifecycle finding is a false positive for this published artifact: its guarded Husky helper is absent, so postinstall performs no mutation. Source inspection shows normal, explicitly invoked chat SDK networking and no concrete malicious chain.
Evidence
package.jsonsrc/index.tssrc/client.tsdist/esm/index.mjs
Network endpoints1
chat.stream-io-api.com
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- `package.json` defines a `postinstall` command.
- `package.json` also defines `prepare`, which runs the package build command.
Evidence against
- The published package has no `scripts/` directory or `scripts/install-husky.mjs`; `postinstall` short-circuits without importing anything.
- `prepare` invokes `yarn run build`; no install-time arbitrary shell, download, or agent-control mutation is present in the published files.
- `src/index.ts` is exports-only, with no import-time filesystem, process, or network action.
- `src/client.ts` sends SDK requests only after client construction and API method use, defaulting to the Stream Chat API host.
- No source use of child-process execution, file writes, credential harvesting, or AI-agent configuration paths was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
2 flaggedpackage.jsonView file
•scripts.postinstall = node -e "require('fs').existsSync('scripts/install-husky.mjs') && import('./scripts/install-husky.mjs')"
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "require('fs').existsSync('scripts/install-husky.mjs') && import('./scripts/install-husky.mjs')"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
1 Critical1 High2 Medium5 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to stream-chat@9.50.2.
See all versions of stream-chat for other recorded verdicts.
- Review the evidence and your use of stream-chat@9.50.2 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.