Togoder security

npm package security report

follow-redirects@1.15.11 security report

No malicious code found.

No issues Version 1.15.11 Files reviewed 4 Size 20.5 KB Scanned

Summary

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

0
critical
0
high
0
medium
0
low

Findings

No findings. The reviewer saw nothing malicious or risky in this version.

Files reviewed

FileVerdictWhat the reviewer saw
debug.js safe Cleared by Jev triage; no further analysis needed
http.js safe Cleared by Jev triage; no further analysis needed
https.js safe Cleared by Jev triage; no further analysis needed
index.js safe The code is the legitimate follow-redirects library with standard HTTP redirection handling, no malicious patterns detected.

Affected version ranges

None of the 3 scanned versions of follow-redirects are flagged high or critical. The latest scanned version, 1.16.1, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.

1.15.91.16.1
VersionsVerdictCountRangeTop findings
1.15.11 โ€“ 1.16.1 No issues 3 >=1.15.11 <=1.16.1
1.15.9 Not scanned 1 1.15.9

Full list, including published versions not scanned yet: version ranges API.

Scanned versions of follow-redirects

VersionVerdictFilesScanned
1.16.1 No issues 4 Oct 4, 2026
1.16.0 No issues 4 Oct 6, 2026
1.15.11 No issues 4 Oct 4, 2026

Frequently asked questions

Is follow-redirects safe to use?

Our AI source review of follow-redirects@1.15.11 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.

Does follow-redirects contain malware?

No malware was identified in follow-redirects@1.15.11 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 follow-redirects checked?

Togoder Security downloaded the published npm package and had an AI model read its 4 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 follow-redirects 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 follow-redirects@1.15.11, cost nothing.

Related security reports