Summary
Togoder Security scanned the npm package es-errors@1.3.0 on Oct 4, 2026. An AI review of 7 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 |
|---|---|---|
| eval.js | safe | Cleared by Jev triage; no further analysis needed |
| index.js | safe | Cleared by Jev triage; no further analysis needed |
| range.js | safe | Cleared by Jev triage; no further analysis needed |
| ref.js | safe | Cleared by Jev triage; no further analysis needed |
| syntax.js | safe | Cleared by Jev triage; no further analysis needed |
| type.js | safe | Cleared by Jev triage; no further analysis needed |
| uri.js | safe | Cleared by Jev triage; no further analysis needed |
Scanned versions of es-errors
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.3.0 | No issues | 7 | Oct 4, 2026 |
Frequently asked questions
Is es-errors safe to use?
Our AI source review of es-errors@1.3.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does es-errors contain malware?
No malware was identified in es-errors@1.3.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 es-errors checked?
Togoder Security downloaded the published npm package and had an AI model read its 7 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 es-errors 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 es-errors@1.3.0, cost nothing.