Summary
Togoder Security scanned the npm package @typescript-eslint/parser@8.70.0 on Oct 6, 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.js | safe | No malicious patterns detected; the file contains standard TypeScript/CommonJS interop helpers, version gating, and re-exports for the typescript-eslint parser. |
| dist/parser.js | safe | No malicious patterns detected; this is the standard @typescript-eslint/parser dist file that parses TypeScript code into an ESLint-compatible AST. |
Scanned versions of @typescript-eslint/parser
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 8.70.0 | No issues | 2 | Oct 6, 2026 |
Frequently asked questions
Is @typescript-eslint/parser safe to use?
Our AI source review of @typescript-eslint/parser@8.70.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @typescript-eslint/parser contain malware?
No malware was identified in @typescript-eslint/parser@8.70.0 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @typescript-eslint/parser 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 @typescript-eslint/parser 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 @typescript-eslint/parser@8.70.0, cost nothing.