Summary
Togoder Security scanned the npm package cookie-es@1.2.3 on Oct 4, 2026. An AI review of 2 source files 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 |
|---|---|---|
| dist/index.cjs | safe | No malicious patterns detected; the code is a standard cookie parsing/serialization library with no network access, command execution, or suspicious file system operations. |
| dist/index.mjs | safe | No malicious patterns detected; the code is a standard cookie parsing/serialization library with no network, filesystem, process, or dynamic code execution behavior. |
Affected version ranges
None of the 2 scanned versions of cookie-es are flagged high or critical. The latest scanned version, 1.2.3, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of cookie-es
Frequently asked questions
Is cookie-es safe to use?
Our AI source review of cookie-es@1.2.3 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does cookie-es contain malware?
No malware was identified in cookie-es@1.2.3 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 cookie-es checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 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 cookie-es 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 cookie-es@1.2.3, cost nothing.