Summary
Togoder Security scanned the npm package decompress-response@6.0.0 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 | The code is a standard decompression stream handler that only processes HTTP response bodies based on content-encoding headers, with no malicious patterns detected. |
Frequently asked questions
Is decompress-response safe to use?
Our AI source review of decompress-response@6.0.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does decompress-response contain malware?
No malware was identified in decompress-response@6.0.0 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 decompress-response 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 decompress-response 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 decompress-response@6.0.0, cost nothing.