# readable-stream@2.3.8 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-04T16:39:58.000Z
- Files reviewed: 17
- Findings: no findings
- Report: https://security.togoder.click/npm/readable-stream@2.3.8
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## Summary

Togoder Security scanned the npm package readable-stream@2.3.8 on Oct 4, 2026. An AI review of 17 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

## Findings

No findings.

## Files reviewed

- `duplex-browser.js` (safe): Cleared by Jev triage; no further analysis needed
- `duplex.js` (safe): Cleared by Jev triage; no further analysis needed
- `lib/_stream_duplex.js` (safe): No malicious patterns detected; this is a standard Node.js core stream Duplex implementation from the readable-stream package.
- `lib/_stream_passthrough.js` (safe): Cleared by Jev triage; no further analysis needed
- `lib/_stream_readable.js` (safe): No malicious patterns detected; this is a legitimate readable stream implementation from the Node.js ecosystem using standard dependencies like process-nextick-args and safe-buffer.
- `lib/_stream_transform.js` (safe): Cleared by Jev triage; no further analysis needed
- `lib/_stream_writable.js` (safe): No malicious patterns detected; this is the standard Node.js Writable stream implementation from the readable-stream package.
- `lib/internal/streams/BufferList.js` (safe): No malicious patterns detected; the code is a standard BufferList implementation used in Node.js internal streams with no network, filesystem, process, or credential access.
- `lib/internal/streams/destroy.js` (safe): No malicious patterns detected; the code is a standard internal stream destruction utility with no exfiltration, credential harvesting, obfuscation, or unauthorized system interaction.
- `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
- `passthrough.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 Node.js stream module shim that conditionally re-exports built-in or local stream implementations without any network, filesystem, or process manipulation.
- `transform.js` (safe): Cleared by Jev triage; no further analysis needed
- `writable-browser.js` (safe): Cleared by Jev triage; no further analysis needed
- `writable.js` (safe): No malicious patterns detected

## 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.

- 4.7.0 (`4.7.0`): medium (Suspicious module path manipulation +2 more)
- 2.3.8 – 3.6.2 (`>=2.3.8 <=3.6.2`): clean
- 2.3.7 (`2.3.7`): not scanned

## Scanned versions

- [4.7.0](https://security.togoder.click/npm/readable-stream@4.7.0): medium, 2026-10-04T16:31:15.000Z
- [3.6.2](https://security.togoder.click/npm/readable-stream@3.6.2): safe, 2026-10-04T16:07:31.000Z
- [2.3.8](https://security.togoder.click/npm/readable-stream@2.3.8): safe, 2026-10-04T16:39:58.000Z

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology