Summary
Togoder Security scanned the npm package readable-stream@3.6.2 on Oct 4, 2026. An AI review of 20 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| errors-browser.js | safe | No malicious patterns detected |
| errors.js | safe | No malicious patterns detected |
| experimentalWarning.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/_stream_duplex.js | safe | This is a legitimate Node.js core stream implementation (Duplex) with standard stream inheritance and no malicious patterns detected. |
| lib/_stream_passthrough.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/_stream_readable.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/_stream_transform.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/_stream_writable.js | safe | No malicious patterns detected; this is a legitimate Node.js core stream implementation. |
| lib/internal/streams/async_iterator.js | safe | No malicious patterns detected; the file is a legitimate Node.js internal implementation of an async iterator for readable streams. |
| lib/internal/streams/buffer_list.js | safe | No malicious patterns detected; the code is a standard buffer list utility with no data exfiltration, credential harvesting, obfuscation, network requests, or other security concerns. |
| lib/internal/streams/destroy.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/internal/streams/end-of-stream.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/internal/streams/from-browser.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/internal/streams/from.js | safe | No malicious patterns detected; the code is a standard utility for converting iterables to streams with no exfiltration, obfuscation, or suspicious behavior. |
| lib/internal/streams/pipeline.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/internal/streams/state.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/internal/streams/stream-browser.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/internal/streams/stream.js | safe | Cleared by Jev triage; no further analysis needed |
| readable-browser.js | safe | Cleared by Jev triage; no further analysis needed |
| readable.js | safe | No malicious patterns detected; the code is a standard readable stream compatibility shim from the Node.js ecosystem. |
Affected version ranges
None of the 3 scanned versions of readable-stream are flagged high or critical. The latest scanned version, 4.7.0, is medium risk. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 4.7.0 | Needs review | 1 | 4.7.0 | Suspicious module path manipulation; Suspicious module resolution |
| 2.3.8 – 3.6.2 | No issues | 2 | >=2.3.8 <=3.6.2 | |
| 2.3.7 | Not scanned | 1 | 2.3.7 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of readable-stream
Frequently asked questions
Is readable-stream safe to use?
Our AI source review of readable-stream@3.6.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does readable-stream contain malware?
No malware was identified in readable-stream@3.6.2 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was readable-stream checked?
Togoder Security downloaded the published npm package and had an AI model read its 20 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan readable-stream together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in readable-stream@3.6.2, cost nothing.