Summary
Togoder Security scanned the npm package issue-parser@7.0.1 on Oct 6, 2026. An AI review of 2 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
Regular Expression Complexity
NPS-B22B78EC4477
The regexes are complex and some loops over regexp.exec or replace could be inefficient, but they are used for parsing references/mentions and do not represent a security vulnerability by themselves.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.js | safe | The code is a text parsing library for issue references and mentions; it does not exfiltrate data, spawn processes, load dynamic code, or access sensitive files. |
| lib/hosts-config.js | safe | Cleared by Jev triage; no further analysis needed |
Frequently asked questions
Is issue-parser safe to use?
Our AI source review of issue-parser@7.0.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does issue-parser contain malware?
No malware was identified in issue-parser@7.0.1 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 issue-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 issue-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 issue-parser@7.0.1, cost nothing.