Summary
Togoder Security scanned the npm package send@1.2.1 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 | No malicious patterns detected; this is the legitimate 'send' npm package for static file serving. |
Affected version ranges
None of the 4 scanned versions of send are flagged high or critical. The latest scanned version, 1.2.1, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 1.2.1 | No issues | 1 | 1.2.1 | |
| 0.19.2 – 1.2.0 | Not scanned | 2 | >=0.19.2 <=1.2.0 | |
| 0.18.0 – 0.19.1 | No issues | 3 | >=0.18.0 <=0.19.1 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of send
Frequently asked questions
Is send safe to use?
Our AI source review of send@1.2.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does send contain malware?
No malware was identified in send@1.2.1 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 send 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 send 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 send@1.2.1, cost nothing.