Summary
Togoder Security scanned the npm package raw-body@3.0.2 on Oct 4, 2026. An AI review of 1 source file 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 |
|---|---|---|
| index.js | safe | Cleared by Jev triage; no further analysis needed |
Affected version ranges
None of the 3 scanned versions of raw-body are flagged high or critical. The latest scanned version, 3.0.2, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 2.5.2 – 3.0.2 | No issues | 3 | >=2.5.2 <=3.0.2 | |
| 1.1.7 | Not scanned | 1 | 1.1.7 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of raw-body
Frequently asked questions
Is raw-body safe to use?
Our AI source review of raw-body@3.0.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does raw-body contain malware?
No malware was identified in raw-body@3.0.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 raw-body checked?
Togoder Security downloaded the published npm package and had an AI model read its 1 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 raw-body 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 raw-body@3.0.2, cost nothing.