Summary
Togoder Security scanned the npm package conventional-commits-parser@6.2.1 on Oct 6, 2026. An AI review of 10 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/CommitParser.js | safe | No malicious patterns detected; the file is a legitimate conventional-commits style commit message parser with no network, filesystem, process, or dynamic code execution activity. |
| dist/cli/index.js | safe | No malicious patterns detected; this is a standard CLI wrapper for conventional-commits-parser using meow and stream pipelines without any suspicious behavior. |
| dist/cli/options.js | safe | No malicious patterns detected; the code only normalizes CLI option strings into regexes and arrays. |
| dist/cli/utils.js | safe | No malicious patterns detected |
| dist/index.js | safe | The file only re-exports local modules and contains an inline source map with no malicious patterns. |
| dist/options.js | safe | No malicious patterns detected |
| dist/regex.js | safe | No malicious patterns detected; the code only constructs regular expressions for parsing commit messages. |
| dist/stream.js | safe | The code is a benign stream parser utility with no malicious patterns such as data exfiltration, credential harvesting, obfuscation, or process spawning. |
| dist/types.js | safe | No malicious patterns detected |
| dist/utils.js | safe | No malicious patterns detected; the code contains only standard string and regex utility functions without network, filesystem, process, or credential access. |
Frequently asked questions
Is conventional-commits-parser safe to use?
Our AI source review of conventional-commits-parser@6.2.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does conventional-commits-parser contain malware?
No malware was identified in conventional-commits-parser@6.2.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 conventional-commits-parser checked?
Togoder Security downloaded the published npm package and had an AI model read its 10 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 conventional-commits-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 conventional-commits-parser@6.2.1, cost nothing.